Tuesday, November 13, 2012

How to add trusted sites via group policy

In the Group Policy Management Editor:

1) Computer Configuration >
2) Policies >
3) Administrative Templates >
4) Windows Components >
5) Internet Explorer > Internet Control Panel > Security Page > Site to Zone Assignment List

Enable it, click Show, add website as value name and 1, 2, 3 or 4 as value.
1. Intranet zone
2. Trusted Sites zone
3. Internet zone
4. Restricted Sites zone

Source: http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/0baa6428-bf48-4e8a-82e1-b961918090d9

Wednesday, October 24, 2012

How To Manually Activate Windows via KMS Server

1) Open an elevated command prompt
2) Type: slmgr /skms {KMS_Server_DNS_Name} than press Enter
3) Type: slmgr /ato

You should receive an Activation Successful message.

Tuesday, October 9, 2012

Determine KMS Server on network

Go into Administrative Tools > DNS.

Open: Server Name > Forward Lookup Zones > "DomainName" > _tcp.

Find the entry with the name _vlmcs and then check the Data Column for the Servers' DNS Name.

Tuesday, March 13, 2012

Cannot map network drives via Logon Script/Group Policy

A very nice explanation regarding the issue where Windows Vista and Windows 7 workstations cannot map network drives via a Logon Script pushed from Group Policy: http://think-like-a-computer.com/2011/06/16/login-scrips-fail-map-drives/

Sunday, February 12, 2012

Hiren's cd fix for lsass and Registry Corruption

(Source: TechSupportForum)

This is what worked for me.

1) System Restore enabled in windows.
2) NTFS Dos Pro and a Boot CD/Disk - Preferabbly Hiren's Boot C (which is loaded with all the apps you need). 
3) Don't use the system.bak file located in windows\repair.
4) Don't assume that either of the _regis~1, ~2, ~3 or ~4 files in a RP\Snapshot folder are the registry files you need - they are not.

1) In your BIOS, set 1st boot device to CD.
2) Reboot with Hiren's Boot CD (or similar).
3) Load NTFS DOS Pro. (in the NTFS Ext2Fs Tools menu on the Hiren CD). You can skip Checkdisk
(use pro instead of regular NTFS as it lists long file name details)
4) Once loaded, the 2nd last line of text indicates the new temporary drive letter of your HDD, in my case D:
5) switch to D:
6)i) You will probably have short file and folder names displayed instead of long when you 'dir', however the full name appears once you are in the directory.
6ii) type (without quotes ' cd system~1\_restor~1\rp95\snapshot '
(RP = restore point, the higher the number the more recent the rp. if this doesn't work for you, try a lower/older number).
7)type ' dir/p ' to list the files in the directory. (use /p, not /w for this)
8) Look through the text (file details) on the right to find ' _REGISTRY_MACHINE_SYSTEM '. Look across to the left, this is the file size (which should be fairly large, eg 5,365,760 in my case). To the left again is the actual file name, in my case ' _r62e7~1 '.
9) You may need to tap the space bar again to finish listing all the files.
10) Once at the command prompt, type ' copy _r62e7~1 d:\windows\system32\config\system '
11) Overwrite = Y
12) Reboot (CTR+ALT+DEL)
13) Load windows.... sucessfully hopefully.

If this doesn't work for you, try;

A) Reload NTFS PRO, go back to the same RP\snapshot directory and copy the following files (copy the actual file name, not the details text).


copy (overwrite) the above files to their corresponding file in the config directory (step 10). eg _REGISTRY_MACHINE_SOFTARE copy over ' software '

Above are all the files that Microsoft recommends you overwrite..... however MS caused my lsass loop in the first place!