NTUSER.DAT.START My Windows 7 logon time could be measured in minutes.  So I tidied up my Roaming Profile.  4GB of space savings later, I was removing the last of the files in the 5 to 20MB range.  One of these files was NTUSER.DAT.START.

NTUSER.DAT is a copy of the user’s HKCU registry settings and is used with Roaming Profiles.

But this NTUSER.DAT.START file?

As it turns out, it’s created by the Citrix UPM product.

NTUSER.DAT is read at profile load and we copy it to NTUSER.DAT.START.

At the end we compare NTUSER.DAT.START and end of session NTUSER.DAT and create a difference file called NTUSER.DAT.NET.

At logoff we merge the changes in NTUSER.DAT.NET (apart from exclusions) into the NTUSER.DAT on the network file share.

At logoff it supposed to be deleted.  In my case it wasn’t, and since I didn’t have any Citrix sessions running, I deleted it.

Using %homeshare% seemed like a good idea at the time.

AD User - Terminal Services Profile We used to hard-code a user’s home directory in a logon script; just like this:

net use H: \\NODDY22\%Username%$

Of course, it becomes a problem when you need to change some of the users to another server.  Say for load balancing.

So you think to yourself, “Oh, I’ll just use the %homeshare% variable!”
(%homeshare% contains the link to the user’s home directory, as stored in Active Directory).

net use H: %homeshare%

All goes fine, until someone logs onto a Citrix/Terminal Server.

“Wahhhh, I don’t have a home drive anymore”.

The cause? In the AD User Properties, you have a Profiles tab AND a Terminal Services Profile tab.

Guess which %homeshare% is loaded when you log on to a Terminal Server?  That’ll be the one in the Terminal Services Profile tab Chucky.  And yes, it was different from the users normal home directory.

Bookmark and Share

“… No Terminal Server License Servers available …”

The remote session was disconnected because there are no Terminal Server License Servers available to provide a license.  Please contact the server administrator.

Strangely enough, I see this error occasionally when I connect to our corporate Citrix server farm.  Googling for the answer, I found Microsoft’s answer, which was less than helpful.

As my (Citrix) server administrators are only two desks away, I asked

“What gives???”

Windows does that, the fix is to delete the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing registry entry.

You can either do that manually, or use the registry file I created here.

Bookmark and Share