Setup KMS Server for Windows Server 2008 R2 or Windows 7

Posted on January 24, 2012 by Ward

Open the command prompt and run the following command:

cscript c: \ Windows \ System32 \ slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Enter the product key xxxxx Windows Server 2008 R2. It is also able to activate Windows 7. The following text appears when the command is successful.

Microsoft ® Windows Script Host Version 5.7
Copyright © Microsoft Corporation. All rights reserved.
Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.
The installation of the KMS server is complete. The server installs itself on port 1688. This port must be opened to be put in the firewall. To change the port the following command can be used.

Slmgr.vbs / SPRT xxxx
Once the firewall is open and the key is installed, the KMS server service has to be restarted. Do this by using the following command:

slsvc & net stop & net start slsvc

To check whether the data will be registered correctly in the DNS, the following command:

nslookup-type = srv _vlmcs._tcp

Here, the following output should appear:

_vlmcs._tcp.test.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms.wardvissers.local
internet address = 192.168.150.7 kms.wardvissers.local

Clients / Servers

The clientele / servers need to connect to the KMS host will automatically find the host by dns. When the client / server using a MAK key is activated. Should this be put back to a KMS client key. These keys are released by Microsoft. When this key is set on the client / server will automatically look for a KMS host. When not present, the client / server activation.

KMS client keys:

Windows 7 Enterprise: 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows Server 2008 Standard: TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Enterprise: YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 R2 Standard – YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise – 489J6-VHDMP-X63PK-3K798-CPX3Y

The following commands can the key be changed from MAK to KMS here are the xxxxx is one of the above keys.

slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Note: To ensure that the client is forced to activate the command to be executed on the client.
slmgr-ato

It can happen that the RMS server returns the following message. This is because the KMS server is just beginning to work with 25 clients and 5 servers.

You can find here the list with error codes & solutions: http://support.microsoft.com/kb/938450

Special thanks to:Harm Hoekstra

VMware View XP persistent disk can not save outlook.ost c:\document and settings\…..

Posted on November 3, 2011 by Ward

I’m busy with created a new a new pool with presentment disks.

The View desktops we’ve got setup are using linked clones and persistent disks which map to the D:\ in the users sessions. Of course this means the users profile is loaded to the D:\ instead of C:\ in the virtual desktops. My issue is, when a new users comes from our old environment into the test view setup, their Outlook is trying to find their OST file on the C:\ (c:\document and settings\…etc). The users data has been loaded to the D:\ though. The only way I’ve found to get around this is going into the Contol Panel in the users session, deleting their Outlook profile,

Solution:

Microsoft saves information about profile under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook

So, within regedit, I right-clicked on HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook then chose Export. For Save as Type, I changed the value to "Text Files (*.txt)". I then opened the text file I created with Notepad. You can’t just search for "Outlook.ost", since there are null, i.e. 00, characters stored between each character. They show up in an ASCII representation as dots. E.g. Outlook.ost would be O.u.t.l.o.o.k…o.s.t.

Since the "Outlook.ost" could be broken across multiple lines, I decided just to search for o.s.t. I found the following in the text file I had created.

Value 31

Name: 001f6610

Type: REG_BINARY

Data:

00000000 43 00 3a 00 5c 00 44 00 – 6f 00 63 00 75 00 6d 00 C.:.\.D.o.c.u.m.

00000010 65 00 6e 00 74 00 73 00 – 20 00 61 00 6e 00 64 00 e.n.t.s. .a.n.d.

00000020 20 00 53 00 65 00 74 00 – 74 00 69 00 6e 00 67 00 .S.e.t.t.i.n.g.

00000030 73 00 5c 00 4a 00 69 00 – 6d 00 5c 00 4c 00 6f 00 s.\.J.i.m.\.L.o.

00000040 63 00 61 00 6c 00 20 00 – 53 00 65 00 74 00 74 00 c.a.l. .S.e.t.t.

00000050 69 00 6e 00 67 00 73 00 – 5c 00 41 00 70 00 70 00 i.n.g.s.\.A.p.p.

00000060 6c 00 69 00 63 00 61 00 – 74 00 69 00 6f 00 6e 00 l.i.c.a.t.i.o.n.

00000070 20 00 44 00 61 00 74 00 – 61 00 5c 00 4d 00 69 00 .D.a.t.a.\.M.i.

00000080 63 00 72 00 6f 00 73 00 – 6f 00 66 00 74 00 5c 00 c.r.o.s.o.f.t.\.

00000090 4f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 5c 00 O.u.t.l.o.o.k.\.

000000a0 6f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 2e 00 o.u.t.l.o.o.k…

000000b0 6f 00 73 00 74 00 00 00 - o.s.t…

I could also have searched in the .reg file I created when I exported the registry information from the other computer. But, again, you can’t just search for "Outlook.ost" in the .reg file you created, either, since the information in it is the hexadecimal representation of the binary data in the registry keys. You would need to convert a string, such as "ost" to hexadecimal form. You can do that at String – ASCII, HEX, Binary Converter. In the String field, I put in ost. The converter showed me the equivalent hex value is 6F 73 74. Note: the converter shows decimal/ASCII, binary, and hex values. Make sure you use the correct one. Also note that the hexadecimal representation of "OST" is not the same as "ost". Since the error message I received referred to Outlook.ost, I converted "ost" to hexadecimal. Again, it may be better to limit the length of the string to reduce the chance it will be broken across multiple lines in the file.

Once you have the hexadecimal equivalent of the ASCII string, you still can’t just search for it, i.e. a search for 6F7374 wouldn’t work. The hexadecimal numbers are stored in the .reg file with commas and the null character, 00, between them. I.e., I would need to search for 6f,00,73,00,74 instead.

In the .reg file found it among the following lines:

"001f6610"=hex:43,00,3a,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,00,74,\

00,73,00,20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,\

67,00,73,00,5c,00,4a,00,69,00,6d,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,20,\

00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,5c,00,41,00,70,00,70,00,\

6c,00,69,00,63,00,61,00,74,00,69,00,6f,00,6e,00,20,00,44,00,61,00,74,00,61,\

00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,5c,00,4f,00,\

75,00,74,00,6c,00,6f,00,6f,00,6b,00,5c,00,6f,00,75,00,74,00,6c,00,6f,00,6f,\

00,6b,00,2e,00,6f,00,73,00,74,00,00,00

I noticed it was associated with a "001f6610" entry. When I had searched the text file, I had also seen Outlook.ost associated with "Name: 001f6610".

You can delete the following registry key with group policy preferences to disable using Offline Folders after disabling Use Cached Mode in Group Policy:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\13dbb0c8aa05101a9bb000aa002fc45a\001f6610

Preventing Automatic Service Pack 1 Update to Windows 7 and Windows Server 2008 R2

Posted on August 16, 2011 by Ward

Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.

Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.

Download

Download details: www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7

The tool can be used with:

Windows 7 Service Pack 1
Windows Server 2008 R2 Service Pack 1

Toolkit Components

The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.

The components are:

A Microsoft-signed executable
A script
An ADM template

Registry key

The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.

Key value name: DoNotAllowSP

When the key value name is not defined, distribution is not blocked.
When the key value name is set to 0, distribution is not blocked.
When the key value name is set to 1, distribution is blocked.

Blocker Script

The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.

When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.

When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.

Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.

Group Policy Administrative Template (.ADM file)

The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.

Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.

Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.

Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.

MMC could not create the snap-in. CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb} error

Posted on August 11, 2011 by Ward

I was able to solve this problem by the procedure below.

1. Navigate to the following directory:

x64 OS
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

x86
C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

2. Copy the ‘machine.config’ file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That’s it Winking smile

How to create a Windows 7 x86 or x64 WMI Filter

Posted on May 6, 2011 by Ward

I want to deploy some applications to different OS versions. I created some WMI filters. I added the right Group Policy to the right WMI filter.

Target Win 7 32 bit machines:

select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND NOT OSArchitecture = "64-bit"

Target Win 7 64Bit machines:

select * from Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType="1" AND OSArchitecture = "64-bit"

Target any 32 bit OS;

SELECT AddressWidth FROM Win32_Processor WHERE AddressWidth =’32′

Target any 64Bit OS:

SELECT AddressWidth FROM Win32_Processor WHERE AddressWidth =’64

GAL Photos in Exchange 2010 and Outlook 2010

Posted on May 5, 2011 by Ward

With Microsoft Exchange 2010 and Outlook 2010 & Lync & Sharepoint 2010 you can finally get photos into your global address list (GAL) and see just who’s who on your emails. You can do this on 2 way’s

1. Using Powershell

A minor schema change

First stop, the AD Schema. A minor schema modification is required to flip the thumbnailPhoto attribute to make it replicate to the Global Catalog.

If you haven’t registered the Schema MMC snap-in on the server you want to make this change on, go ahead and do so using the following command:

Regsvr32 schmmgmt.dll
Fire up a MMC console (Start -> Run -> MMC) and add the Schema snap-in
In the Active Directory Schema snap-in, expand the Attributes node, and then locate the thumbnailPhoto attribute. (The Schema snap-in lists attributes by its ldapDisplayName).
In the Properties page, select Replicate this attribute to the Global Catalog, and click OK.

Figure 1: Modifying the thumbnailPhoto attribute to replicate it to Global Catalog

Loading pictures into Active Directory

Now you can start uploading pictures to Active Directory using the Import-RecipientDataProperty cmdlet, as shown in this example:

Import-RecipientDataProperty -Identity "Ward VIssers" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\wardvissers.jpg" -Encoding Byte -ReadCount 0))

To perform a bulk operation you can use the Get-Mailbox cmdlet with your choice of filter (or use the Get-DistributionGroupMember cmdlet if you want to do this for members of a distribution group), and pipe the mailboxes to a foreach loop. You can also retrieve the user name and path to the thumbnail picture from a CSV/TXT file.

2. Using a Free tool like Outlook Photos from Exclaimer

Download the Tool HERE

The tool is easy to use Smile .

Prerequisites

User Preferences

Domain user – The logged in user’ account is required to be an Active Directory account.

Domain computer – The computer the user is logged into needs to be joined to an Active
Directory domain.

Active Directory permissions – The logged in user must have permission to upload photos to the required Active Directory accounts. (Alternate credentials can be supplied or control of the thumbnailPhoto field can be delegated to the logged in user.)

Operating System

Windows Server 2003 x86 (including all service pack levels).
Windows Server 2003 R2 x86 and x64 (including all service pack levels).
Windows Server 2008 x86 and x64 (including all service pack levels).
Windows Server 2008 R2 x86 and x64 (including all service pack levels).
Windows Small Business Server 2003 (including all service pack levels).
Windows Small Business Server 2008.
Windows Small Business Server 2011.
Windows XP x86 and x64 (including all service pack levels).
Windows Vista x86 and x64 (including all service pack levels).
Windows 7 x86 and x64 (including all service pack levels).

Other Software

Microsoft Outlook 2010 x86 and x64

Microsoft .NET Framework 3.5 SP1

Microsoft Exchange 2010 RTM and above

Active Directory

You must be logged into an Active Directory domain to run the application.

Active Directory Forest
Domain and Forest functional level of Windows Server 2008 and above.
For Domain or Forest functional level of Windows Server 2003, the Windows Server 2008 Forest preparation must first be complete.

Screenshots

Microsoft Virtualization for VMware Professionals Jump Start

Posted on April 26, 2011 by Ward

The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational Smile

Download all the Video’s:
Video: WMV | WMV (ZIP) | PSP
Audio: WMA | MP3

Now only finding some spare time to watch’s these video’s Winking smile

Windows Server 2008 R2 Hyper-V SP1 Component Architecture Poster

Posted on April 15, 2011 by Ward

This poster provides a visual reference for understanding key Hyper-V technologies in Windows Server 2008 R2 Service Pack 1. It focuses on architecture, snapshots, live migration, virtual networking, storage, RemoteFX and Dynamic Memory.

To download the poster click on the picture

Hyper-V Server 2008 R2 SP1 ready for download

Posted on April 15, 2011 by Ward

Hyper-V Server 2008 R2 with SP1 included is now ready for download:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=92e2c4ba-6965-4f8e-abbe-cbb40556b680

Poster: Deploying Windows 7 in Enterprise

Posted on March 29, 2011 by Ward

To download just click on the picture.

Ward Vissers

Things About Microsoft & Exchange & VMware

Category Archives: Windows