M.T.C.

Just to update the issue. M.T.C. staff technicians have come across a solution specific to Remote Desktop Services in 2008 R2. In order to properly bind the certificate to the remote desktop service the user must install the certificate correctly either via MMC or IIS or etc. and then proceed to Start>Administrative Tools>Remote Desktop Service> Remote Desktop Session host configuration. In this MMC you will have the option to physically right click the RDP connection node being used and enter its properties. Under the general tab one can choose SSL and then near the bottom there is Select button just below the words Certificate: which will allow you to choose the proper SSL cert and stop the RDS service from creating a new cert each it connects.

DHCP Options in Windows Server 2008 ( the items which the server sends and looks data for) do not always have the options needed available out of the box, but thanks to the team over at Cisco adding options have never been easier. Using an older guide which was created for Cisco IP phones that shows a user on Windows 2000 how to add new options to the server. The procedure for Server 2008 is actually the same minus the GUI/DHCP location changes.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00800942f4.shtml

When using any virtual machines that are not in the default system folder, Windows Hyper-V Management Console will have trouble taking snapshots for the VHD unless proper permissions are in place. In order to avoid broad insecure access at  minimum the folder and drive should have complete access to these accounts System, Authenticated Users, Domain Admin/Administrators. These settings should solve simple authentication issues for doing various management tasks.

One of our data centers is housing a test machine which was running some email accounts and some new pbx’s for us in Hyper Visor mode perfectly until a power loss which extended the sections UPS units beyond their capacity and thus caused a power loss. So our technicians were not to distraught thinking there should  be no big issues in restoring the test center back into action. After the systems returns online we have noticed that the box with the exchange server has vanished clearly from the Hyper-V manager screen.

The testing team panicked before assessing the situation. We recommend you to really look at the situation when it comes to dealing with Virtual Machines before applying any fixes. Our primary focus is to always backup the machines (even broken) as they are before any fixes are done. Next remember that the V-machines though dependent on each to operate correctly (file structure wise) can be rebuilt by replacing some missing pieces to a machine. Think of it this way you have lost the case and the motherboard to your computer but you still have the hard drives perfectly intact. After a simple rebuild of the machine and the correct snapshot chosen as a hard drive the test center was back online. So lesson learned before delaying a situation and panicking, we recommend to always assess your possibilities and step out of the box to see quick resolutions.

Recently, Microsoft has implemented in a new solution for VPN configuration which allows users to combat network security when traveling by accessing the network on standard HTTPS port (443). Utilizing SSL technology, server certificates are now used to ensure proper communication is occurring. After reading various online configuration guides and books available in stores, administrators will still face a rather daunting task of enabling a rather easy configuration for production use. What MTC has found is that some steps are missing to ensure that proper SSL binding is done to the machines. Thanks to technet.com we are able to provide you with a link which solve almost all common SSTP protocol problems. HAPPY VPNING!

http://blogs.technet.com/rrasblog/archive/2007/11/08/do-you-want-to-change-the-certificate-used-by-the-sstp-server-read-how.aspx

Microsoft has not designed the access of the integration components to be easy for whatever reason that may be. Microsoft requests/requires one to access the components while signing up at connect.microsoft.com. The tragedy of the situation is once a user does complete the setup and sign in process they will only find that the links to the components are far buried in a forum then readily available on the Integration Components Page for http://connect.Microsoft.com . In order to save you time we here at M.T.C are providing you with the links directly thanks to DasGood in the connect forums!

Linux Integration Components for Windows Server 2008
Hyper-V:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ab7f4983-93c5-4a70-8c79-0642f0d59ec2

Linux Integration Components for Windows Server 2008 Hyper-V
R2

http://www.microsoft.com/downloads/details.aspx?familyid=C299D675-BB9F-41CF-B5EB-74D0595CCC5C&displaylang=en