Pat Spencer

Fix Trust Relationship if a simple Computer password reset is required http://blog.blksthl.com/2013/03/18/fix-the-trust-relationship-between-this-workstation-and-the-primary-domain-failed/ This is dead simple, but if you were not aware, you do not necessarily need to rejoin the domain if the trust relationship is broken with AD.  Just resetting the password is all . Steps using Powershell: Login locally to the server Run the PowerShell command: Reset-ComputerMachinePassword -Server -Credential Restart-Computer

Found this great article. http://blog.scosby.com/post/2012/12/13/Disabling-Windows-Server-2012-Lock-Screen-Timeout.aspx Disabling the Windows Server 2012 Lock Screen Timeout In Server 2012 by default, the lock screen will put the monitors to sleep after 1 minute. I found myself waking the monitors too frequently. An initial web search led me to a MSDN forum post for Windows 8 that unlocked a missing Power Settings feature in Server 2012.   1.        Open the following registry key      a.        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\7516b95f-f776-4464-8c53-06167f40cc99\8EC4B3A5-6868-48c2-BE75-4F3044BE88A7     2.        Set the following value      a.        Attributes => 2   3.        Now open Control Panel>Power Options>Change Plan Settings...

This article explains how to configure your Windows Server 2008 R2 Active Directory Primary Domain Controller to synchronize time with an external time source. Note: In an active directory, all member computers will sync time with the PDC, so you only need to setup an external time source on the PDC. Open an elevated command prompt and type the following: Net Stop W32Time W32tm /config /syncfromflags:manual /manualpeerlist:" " W32tm /config /reliable:yes Net Start W32Time W32tm /config /update W32tm /resync You can run W32tm /resync on member computers to sync time with the PDC. A good reliable time source to use is pool.ntp.org . Check out the NTP Project for world wide time sources. Also note:  from Microsoft: http://support.microsoft.com/kb/816042

With the following registry additions, you can create a new URL protocol handler for PowerShell: This allows me to do the following: Start -> Run: ps:3+5 Start -> Run: ps:get-process Start -> Run: ps: A new powershell window opens, parses and executes the command and leave the window open. Import the following to set it up: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS] @=" URL:Powershell Protocol" "URL Protocol"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\DefaultIcon] @="\"C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\powershell.exe\",1" [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell\open] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PS\shell\open\command] @="\"C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\powershell.exe\" -NoLogo -NoExit -command $ExecutionContext.InvokeCommand.InvokeScript('%1'.Substring(3))" Special thanks ...

The default install of DIRSYNC will synchonize your entire AD with Office365. To my way of thinking, this is excessive and unnecessary. During the install, at the end of following running Configuration Wizard, you will be asked if you wish to "Synchronize now".   Uncheck this box and then, after a reboot, follow the instructions below: Step 1: Create a shortcut to C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\miiclient.exe (Synchronization Service Manager) Change the advanced properties to Run as Administrator .  Launch this tool Step 2: After the install,  Open Active Directory Users and Computers and search for all users starting with "MSOL_".  You will see that there is a new account called "MSOL_6b06ffadffb5" or some such giberish.  The number is different on every Server.   Change the password on this account to something secure, that you can enter in the Service Manager Step 3:  In Synchron...

To display devices when you click Show hidden devices : Click Start , point to All Programs , point to Accessories , and then click Command Prompt . At a command prompt, type the following command , and then press ENTER: set devmgr_show_nonpresent_devices=1 Type the following command a command prompt, and then press ENTER: start devmgmt.msc Troubleshoot the devices and drivers in Device Manager. NOTE : Click Show hidden devices on the View menu in Device Managers before you can see devices that are not connected to the computer.

Some DNS name queries are unsuccessful after you deploy a Windows Server 2008 R2-based DNS server.  It seems inconsistent but it all depends on the DNS Name being called.  (BMO.COM always exhibits the problem) http://support.microsoft.com/kb/832223   Scenario: Clear DNS cache on the server: dnscmd /clearcache Run NSLOOKUP Set type=all BMO.COM Notice that the first attempt times out.  Repeated attempts will eventually be successful. Workaround: Type: dnscmd /config /enableednsprobes 0  

How to fix “AnyConnect was not able to establish a connection” or “VPN client driver encountered an error” Cisco AnyConnect VPN error messages. Found this on another blog post, so I won't take credit for it. Just put the following in a .REG file and import it.   Windows Registry Editor Version 5.00 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpnva] "DisplayName"="Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64" Also, see: http://furycomputing.wordpress.com/2012/12/29/how-to-fix-anyconnect-was-not-able-to-establish-a-connection-or-vpn-client-driver-encountered-an-error-cisco-anyconnect-vpn-error-messages/ Symptom : After installing (or Re-installing) the Cisco AnyConnect Client on Windows 8, unable to initialize the NIC.  Error is “AnyConnect was not able to establish a connection to the specified secure gateway.  Please try connecting again” The Fix is to correct an error in the Description string for the VPN Connection in the registry....

Re: Citrix Receiver 3.1 spawning multiple SelfService.exe processes Update 7/12/2013: I am told that this issues has been fixed with the latest release of the receiver, Version 4.  It was released June 26, 2013 Current Info: Download and install version 4.0 of the receiver.  http://www.citrix.com/downloads/citrix-receiver.html Previous Info: Fix 1) Download the Citrix Receiver and install it with the following command line: CitrixReceiver.exe ADDLOCAL=ReceiverInside,ICA_Client,USB,DesktopViewer,Flash,Vd3d /silent This will install everything BUT selfservice.exe Fix 2) Or if the installation file is called CitrixReceiverWeb.exe, enter the following command line: CitrixReceiverWeb.exe ADDLOCAL=ReceiverInside,ICA_Client,USB,DesktopViewer,Flash

NLB requires configuring a Static ARP for the virtual MAC address of the Cluster Resource. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006525

The default AD Tombstone lifetime in Windows 2003 AD is 60 days. This was raised to 120 days in AD on Windows 2008 You can increase the lifetime before tombstoning an AD Object using the following: http://www.petri.co.il/changing_the_tombstone_lifetime_windows_ad.htm

Discovered today that you need to create a GPO to allow the account “NT Virtual Machine\Virtual Machines” to logon as a service. Without this, you will discover that eventually you will not be able to start a VM.   It will give a Logon denied error message. Install the GPMC on a Hyper-V server Create or modify an existing GPO to include the above account in the LOGON AS A Service policy Run GPUPDATE /FORCE on all Hyper-V servers.

Using your computer without a mouse http://www.wikihow.com/Use-Your-Computer-Without-a-Mouse Before anyone flames me, this was required for me to install a Windows Server 2003 Pre-SP1 as a VM on Hyper-V 2012.  This was required for a migration lab.  You are unable to install the Integration Tools until SP2 is installed.