Comments on: Shared User Profiles – Staging Scripts

By: wackyraces

wackyraces — Sun, 18 Mar 2012 09:06:26 +0000

Too many zeros, 15,000 devices!

By: wackyraces

wackyraces — Sun, 18 Mar 2012 09:05:24 +0000

I did modify the script to improve some of the coding, which has speeded the process up. Overall though it has been excellent and well done in writing it originally. We tested it in a pre-prod environment fully before going into production. We are quite large, 15,0000 devices and 30,000 users. So far we have done over 8,000 devices with not many issues at all. Support are pleased with it as if there are any issues, they can fix it quite easily. I’m just modifying the script to check for the last login time of the profiles, as we will be using the script on some of our very slow WAN sites soon. Many thanks.

By: dwarfsoft

dwarfsoft — Thu, 15 Mar 2012 10:00:25 +0000

Thanks for the feedback. I’m so glad to see that this actually reached production somewhere. The project that I produced this for stagnated and I left the company and moved on without ever seeing it work on a large scale (80,000 End users, probably about 20,000 PCs/Laptops).

This script could have been modified so that it only staged the DLU profiles once, thereby making it run through quicker with each subsequent attempt. You could just put a Registry value into the ProfileList\{GUID} path and manage this, or in any other place in the registry that suits for that matter (HKLM\Software\ProfileStaging\userid).

Thanks for the feedback.

Cheers, Chris.

By: wackyraces

wackyraces — Wed, 14 Mar 2012 21:01:18 +0000

Many thanks for responding. I shall test the script and then insert it into the main staging script. So far the staging script has been really great. It has solved our issue in moving the DLU accounts to AD accounts on the devices.

By: dwarfsoft

dwarfsoft — Wed, 14 Mar 2012 20:48:23 +0000

I covered load time of profiles here: http://www.dwarfsoft.com/blog/2010/04/22/last-login-time/
The Script you would want is:

DIM oNet, strComputerName, strUserName, strUserDomain
SET oNet = CreateObject("WScript.Network")
strComputerName = oNet.Computername
strUserName = oNet.UserName
strUserDomain = oNet.UserDomain
SET oNet = nothing
 
Set WMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
 
SubKey = ""
 
Set wmiCol = WMI.ExecQuery ("SELECT Domain, Name, SID FROM Win32_Account where Name="""&strUserName&""" And Domain="""&strUserDomain&"""")
For each wmiItem in wmiCol
  SubKey = wmiItem.SID
  Exit For
Next
tz = 0
For Each os In GetObject("winmgmts:").InstancesOf ("Win32_OperatingSystem")
  tz = os.CurrentTimeZone
  Exit For  
Next
 
Const HKEY_LOCAL_MACHINE = &H80000002
 
strReturn = ""
 
Set objReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv"  )
strKeyPath = "SOFTWARE\MICROSOFT\Windows NT\CurrentVersion\ProfileList\" & SubKey 
 
strValueName = "ProfileLoadTimeHigh"
Return = objReg.GetDWORDValue(HKEY_LOCAL_MACHINE,strKeyPath,strValueName,lngHighValue)
strValueName = "ProfileLoadTimeLow"
Return = objReg.GetDWORDValue(HKEY_LOCAL_MACHINE,strKeyPath,strValueName,lngLowValue)
If typename(lngHighValue) <> "Null" then
  NanoSecs = (lngHighValue * 2 ^ 32 + lngLowValue)
  '' /* Returns time in Workstation Timezone */
  DT = #1/1/1601# + (NanoSecs / 600000000 / 1440) + (tz / 1440)
  strReturn = CDate(DT)
End if

Restructure and throw that in a function that instead of finding the current user uses whatever ‘Subkey’ you pass to it and returns the last login time. That should be quick as it need only do a couple of registry reads and some math. If I had time I’d script it up, but everything you need is here already

Then you can do a DateDiff between now and the returned date.

Cheers, Chris.

By: wackyraces

wackyraces — Wed, 14 Mar 2012 14:52:49 +0000

Many thanks for the excellent scripts. They work really well. On some of our devices, we can have up to 50 local user profiles. This means that the script can take a long time to run. Is there a way to alter the script so that it would only migrate accounts that have a last login time of 60 days or less. I have had a good attempt but have not been successful. Thanks.

By: dwarfsoft

dwarfsoft — Mon, 03 May 2010 01:28:15 +0000

Hi,

Well, to put the script together you simply create a VBScript file that includes all the functions, then call StageAllUsers passing the domain FQDN and the Netbios Domain.

Const HKEY_LOCAL_MACHINE = &H80000002
ADFQDN = GetDomainFQDN()
ADDomain = GetDomainShortName()
 
If ADFQDN  "" Then
    ret = StageAllUsers(ADFQDN,ADDomain)
End If
 
'**************************************************************************************************
' Get the Workstations Domain FQDN (if it has one)
' Returns "" if the machine is a not a member of a domain
Function GetDomainFQDN
    GetDomainFQDN = ""
    Set objWMISvc = GetObject( "winmgmts:\\.\root\cimv2" )
    Set colItems = objWMISvc.ExecQuery( "Select * from Win32_ComputerSystem", , 48 )
    For Each objItem in colItems
        strComputerDomain = objItem.Domain
        If objItem.PartOfDomain Then
            GetDomainFQDN = strComputerDomain
        Else
            ' Workgroup Computer, Ignore it
        End If
    Next
End Function
 
 
'**************************************************************************************************
' Get the Workstations Domain Short Name (if it has one)
' Returns "" if the machine is a not a member of a domain
Function GetDomainShortName
    GetDomainShortName = ""
    Set objWMISvc = GetObject( "winmgmts:\\.\root\cimv2" )
    Set colItems = objWMISvc.ExecQuery( "Select * from Win32_ComputerSystem", , 48 )
    For Each objItem in colItems
 
        If objItem.PartOfDomain Then
            Set objSystemInfo = CreateObject("ADSystemInfo") 
            GetDomainShortName = objSystemInfo.DomainShortName
        Else
            ' Workgroup Computer, Ignore it
        End If
    Next
End Function

From there you simply package it so it installs on the Workstations, then get it to run after every logon. This way the domain accounts and the local accounts are synchronized.

I have uploaded the VBS script into the original Article now.

If, however, you do not need to worry about rollback then you can simply use the User State Migration Tools that Microsoft has provided to convert the user accounts to Domain accounts (which is much simpler).

Cheers, Chris.

By: droberts

droberts — Fri, 30 Apr 2010 18:30:55 +0000

I am interested in using this script, as I work for a school district who is migrating from Novell to AD but I’m not sure how to put it together and how to run it. Could you provide some more info?

Thanks,
Dustin Roberts

By: Last Login Time - Dwarfsoft [GPA]

Last Login Time - Dwarfsoft [GPA] — Thu, 22 Apr 2010 01:54:42 +0000

[...] the issue manually. As I have had a fair bit of experience with Windows Profiles recently (see the last blog post) I was familiar with the ProfileLoadTimeHigh and ProfileLoadTimeLow registry keys in the [...]