Some of applications require additional SQL Server 2008 or 2012 fetures installed. Some of these features might not be available in standard setup of SQL Server. In that case you have to refer to Microsoft Dowloads web page in order to download additional components required for installation:
Unfortunately there is a problem when you try to add .Net Framework 3.51 to Windows Server 2012 using Server Manager. In order to fix that issue and get .Net Framework 3.51 installed (which is required by majority of applications and servers) issue following command from Command Prompt:
dism /online /enable-feature /all /featurename:NetFX3 /source:x:\sources\sxs
Please notice that x: in source parameter has to be replaced with appropriate drive letter for DVD with Windows Server 2012 installation files.
In order to assign static IPv4 address to Windows Server 2012 Core using power shell use:
New-NetIPAddress -IPAddress 172.16.48.11 -InterfaceAlias "Ethernet" -DefaultGateway 172.16.48.5 -AddressFamily IPv4 -PrefixLength 24
Recently I came up with idea to upgrade operating system on my HP TouchSmart tm2t to Windows 8. In general there was no major issues except one. As this computer has two graphics adapters (Intel for low performance when operate on battery, AMD/ATI for better performance when operate on mains) there was small issue with configuring Switchable Graphics option.
After installation computer was operating only on low performance Intel card and thre was no possibility to switch to AMD/ATI. Here is what I’ve done ot make it work:
If you want to use Windows Server 2012 Datacenter on workstation/laptop (sometimes it is handy to have mobile workstation with server operating system) you might experience issues with wireless networking. Even if driver for wireless network adapter is installed you might not be able to connect to any wi-fi network.
In order to use wireless in Windows Server 2012 Datacenter additional feature has to be installed: Wireless LAN Service. This can be installed from PowerShell prompt using add-windowsfeature wireless-networking command, as shown on screenshot below:
Once installed and server rebooted make sure that WLAN AutoConfig service is started, as shown on screenshot below:
Sometimes when ShoreTel ShoreGear switches connected to infrastructure might have old version of the firmware. In theory ShoreTel HQ Director should upgrade firmware on devices to bring it to current version across the infrastructure. However sometimes that fails and there is a need to enforce apropriate firmware on device.
In order to enforce firmware on ShoreTel switch best is to logon to ShoreTel HQ Director server and issue burnflash command as shown below:
C:\Program Files\Shoreline Communications\ShoreWare Server>burnflash -switch 192.168.20.31
Shoreline Communications BurnFlash Utility (Version 14.21.4905.0)
Burning flash for switch "192.168.20.31" (192.168.20.31).
Current switch info:
Internet Address: 192.168.20.31
Ethernet Address: 00-10-49-00-00-00
Product Code: IPBX-SG4_T1
Firmware Version: 12.5.8107.0
Patch Level: 0
BootRom Version: 1.1.3.17
Up Time: 0 days 00:28:21 (booted from Flash)
POST Version: 3
TMS 5460: NccBurnFlash(...,0,192.168.20.31): Start
TMS 5460: : FileA Type=2,Unit=0,Language=
TMS 5460: : FileB Type=2,Unit=2,Language=en-US
TMS 5460: NccBurnFlashWorker2[192.168.20.31]: WSASocket() --> 1616 (Error: 0)
12.50 MBytes (100%) transferred to flash unit 0.
TMS 5460: NccBurnFlashWorker2[192.168.20.31]: WSASocket() --> 1616 (Error: 0)
1.13 MBytes (100%) transferred to flash unit 2.
Rebooting switch.
TMS 5460: NccBurnFlash[192.168.20.31]: End. hr = 0x0
Waiting up to 180 seconds for switch to start.
Waited 103.4 seconds ... connected.
Current switch info:
Internet Address: 192.168.20.31
Ethernet Address: 00-10-49-00-00-00
Product Code: IPBX-SG4_T1
Firmware Version: 14.21.4905.0
Patch Level: 0
BootRom Version: 1.1.3.17
Up Time: 0 days 00:00:00 (booted from Flash)
POST Version: 3