IT Information that works!

Quickly Convert from Core to GUI Stop the command line madness! Windows Server 2012 R2 on a VMWare vSphere 5.5 Virtual Machine After accidentally installing a Windows Server 2012 R2 Core only version for my new Exchange 2016 server I went searching on the internet for the correct process to convert from Windows Server 2012 R2 Core to GUI. A quick search revealed numerous web sites with the knowledge needed to go from Windows Server 2012 R2 Core to GUI. However, none of them worked for me. I tried this command and that. I found the correct index and used that in the next command however the process always failed with and error. Error Message: Install-WindowsFeature : The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed.  The source files could not be downloaded.  Use the source option to specify the location of the files that are required to restore the feature. Error:

Snom PA1 - Unable to update firmware I recently bought 2 new Snom PA1’s to use as intercoms with our Lync 2013 environment. One install went fine while the other had some issues. On the first PA1 I upgraded the firmware to the latest version, 8.7.5.35, from here: http://wiki.snom.com/Snom_PA1/Firmware Unfortunately, this version does not work with Lync 2010 or 2013. You must install the UC Edition firmware in order for the Snom PA1 to work correctly with Lync 2010 or 2013. On the second Snom PA1 I updated the firmware directly to UC Edition 8.8.2.26, from here: http://downloads.snom.com/snomuc/snomPA1-UC-8.8.2.26-SIP-f.bin The upgrade worked fine and I was able to configure the PA1 and integrate it into my Lync 2013 environment. I then went to upgrade the first Snom PA1 to the UC Edition from the current 8.7.5.35. I went to Setup >>> Software Update and pasted in the URL http://downloads.snom.com/snomuc/snomPA1-UC-8.8.2.26-SIP-f.bin . I the

Lync 2013 Toll Free Dial Plan Rules Toll Free Translations   It took me a while to track down, test, and modify these toll free number rules before they finally worked for my environment. So if you are having the same problem with users calling toll free numbers try these Dial Plan rules.   Toll Free (10 digit) Toll free no +1   ^(8(00|88|77|66|55|44)\d{7})$ Toll Free (11 digit) Toll free no +    ^1(8(00|88|77|66|55|44)\d{7})$ Toll Free (12 digit) Toll free with +1 ^\+1(8(00|88|77|66|55|44)\d{7})$   Each rule covers any toll free number that uses 800, 888, 877, 866, 855, and 844. This includes all know toll free numbers in North America. If the user dials a 1 or a +1 before the toll free number the 1 or +1 will be stripped before it is sent to the SBC or the phone company within Lync 2013.   Examples:   Dialed number: (888) 555-5555 will get translated to: 8885555555   Dialed number: 1 (800) 555-5555 will get translated to: 8005555555   Dialed number: