guy labs guy labs

VMware Snapshot and recovery: fix active directory replication

Windows
/by
Two weeks ago I tried to install the newest updates onto one of our virtual domain controllers. Shortly explained it was not the best idea and I had to recover to the snapshot taken just before I launched the update process, lucky enough I remembered to take one. :) Yesterday morning I was told that the active directory content was different on both domain controllers. I found that hard to believe and had to take a look myself and yes, the content was different. How did that happen? I knew recovering from a snapshot may result in issues but I didn't see it in the first place. After looking around I found out I had a so called USN rollback to do because of a "dirty" rollback of the active directory. Microsoft is aware of the issue and has posted an article about it: http://support.microsoft.com/default.aspx?scid=kb;EN-US;875495 So the way would have been demoting and promoting a domain controller, and this during the day? No way... there had to be another solution. So I checked the replication status: Result was: This was odd, I checked the USN on both machines and they were identical. So the replication was not a total failure, but somehow not working as usual. Next I wanted to make sure the inbound and outbound replication were working and that the global catalog was still working: And there it was, the output revealed the problem: Inbound and outbound replication were disabled on the recovered virtual domain controller. So enabling those two parameters did the trick: After waiting...

Introducing DHCP Failover in Windows Server 2012

Windows
/by
One of the most central feature there is within a private network, not depending on size or architecture, is DHCP. Until today Windows server was not able to have a failover feature implemented, only exception was to include the feature in a Windows failover cluster. But not anymore: it became a feature in Windows server 2012. Of course it only runs on Windows server 2012 so you will have to upgrade your two servers first which will hold the two DHCP roles. After you successfully upgraded: 1. Install the DHCP role on the server1 and set up the first DHCP server according to your needs. Authorize the server and create your DHCP scopes. 2. Switch onto the server2 and install the DHCP role as well. Authorize the server. 3. Switch back onto server1 and right-click “configure failover” (IMAGE) 4. When asked for partner server enter the FQDN of server2 and click “Next” 5. Give the relationship a name, enter a shared secret for the relationship to use and click “Next” 6. Leave settings for MCLT*, change operation mode to “hot standby” and finish wizard VoilĂ , that’s all there is to do. You’re set up for DHCP failover, do not forget to present the IP address of the second DHCP server to all your other components. For more detailed information and all powershell commands to realize this cool new feature on server core visit the following link from the Microsoft Technet: http://blogs.technet.com/b/teamdhcp/archive/2012/06/28/ensuring-high-availability-of-dhcp-using-windows-server-2012-dhcp-failover.aspx   Picture: http://technet.microsoft.com   *Definition of MCLT (Technet): The Maximum Client Lead Time (MCLT) is additional time provided to a DHCP client...

Logon credentials issue after Windows 8 upgraded to 8.1

Windows
/by
When setting up Windows 8 I decided to create a local user, I’m not a big fan of the live ID. The live ID is mandatory for the store, but if you don’t use the store the live id is mostly useless. Microsoft really does not need to know everything, we have Google for this. Anyway, after upgrading to Windows 8.1 I was a bit surprised that I had to log on to my Windows with my live ID again. And surprisingly I was not able to change back to my locally created user. This was an absolute no go and after some search I found a work around from a member of the technet. Follow this procedure to disconnect from your windows live id to get back onto your local account: Move your mouse to the upper right corner, click on settings, then change PC settings Select accounts in the left menu Below your windows live account click disconnect This opens a box giving you the opportunity to log on to your local account again. If you don’t have upgraded yet you can avoid this from happening by unplugging your network connection. Also you have the opportunity to create a local user when setting up windows 8.1 from...