Using different OU's for an AD domain join

Written on 06 August 2014.

In phase2 of an ENGL Imaging Toolkit's build process a machine is joined to AD, if you have configured the 'Active Directory / Workgroup' options in your ENGL project.

Sometimes you need to register a device in more than one OU. This little vbscript, to be run in phase2-before, set two variables AD_REGISTRATION_OU and AD_REGISTRATION_DOMAIN. These variables then can be used as %AD_REGISTRATION_OU% and %AD_REGISTRATION_DOMAIN% in your ENGL project.

In this vbscript the default gateway of the IP adapter is being read, using WMI. Based on the default gateway the two variables are set accordingly. You can also use other adapter properties, which are described in this MSDN article about the Win32_NetworkAdapterConfiguration class.

SetADRegistrationOU()

Function SetADRegistrationOU

on error resume next

Status = Utils.AppendLog("phase2-before.vbs: " & "SetADRegistrationOU()")

Dim strDefaultGateway
Dim oDG, oDGs, WMI

strDefaultGateway = Empty
Set WMI = GetObject("winmgmts:\\.\root\cimv2")
Set oDGs = WMI.ExecQuery _
("Select * from Win32_NetworkAdapterConfiguration where IPEnabled=TRUE")

For Each oDG in oDGs
    If Not IsNull(oDG.DefaultIPGateway) And Not oDG.defaultIPGateway(0) = "0.0.0.0" Then
       strDefaultGateway = oDG.DefaultIPGateway(0)
       Exit For
    End If
Next

Status = Utils.AppendLog("phase2-before.vbs: " & " default gateway is: " & strDefaultGateway)

select case strDefaultGateway
   case "10.114.0.1"
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_OU", "ou=workstations,ou=rovabu hq,dc=rovabu,dc=nl")
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_DOMAIN", "rovabunetworks.nl")
   case "10.101.0.1"
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_OU", "ou=laptops,ou=rovabu hq,dc=rovabu,dc=nl")
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_DOMAIN", "rovabunetworks.nl")
   case Else
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_OU", "ou=workstations,ou=rovabu hq,dc=rovabu,dc=nl")
     status = Utils.SetSystemEnvironmentVariable("AD_REGISTRATION_DOMAIN", "rovabunetworks.nl")
end select

If Err.Number <> 0 then
    MsgBox "An error occured in routine SetADRegistrationOU()"
    Status = Utils.AppendLog("phase2-before.vbs: " & "SetADRegistrationOU()" & " an error occurred " & Err.Number)
Else
    Status = Utils.AppendLog("phase2-before.vbs: " & "SetADRegistrationOU()" & " successfully")
End If

End Function

Add new comment

Allow remote connections to this computer

Written on 21 July 2014.

When you deploy Windows Server 2012 using an ENGL Imaging Toolkit project for Windows Server 2012, you can include in a phase1-after.ps1 powershell script to enable 'Remote Connections':

Use these three commands in phase1-after.ps1:

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication -Value 1
Set-NetFirewallRule -DisplayGroup 'Remote Desktop' -Enabled True

The first two commands take care of setting the correct registry keys.
'Set-NetFirewallRule' changes your firewall settings in order to allow using 'Remote Desktop' through your firewall.

Add new comment

Appending slmgr.log to ztoolkit.log

Written on 24 June 2014.

In phase4 of an ENGL Imaging Toolkit's build process a device is activated using either a MAK key or KMS server. The activation log is driven by slmgr.vbs and saved in a file called c:\ztoolkit\slmgr.log.

For troubleshooting purposes it might be convenient to have this information in ztoolkit.log as well. This little vbscript, to be run in phase4-after.vbs, appends the slmgr.log to ztoolkit.log:

AppendSlmgrLogfile()

Function AppendSlmgrLogfile

on error resume next

Set FSO = CreateObject("Scripting.FileSystemObject").OpenTextFile("c:\ztoolkit\slmgr.log",1)
strSlmgrLogging = FSO.ReadAll()
FSO.Close

Status = Utils.AppendLog("phase4-after.vbs: " & strSlmgrLogging )

If Err.Number <> 0 then
    'MsgBox "An error occured in routine AppendSlmgrLogfile()"
    Status = Utils.AppendLog("phase4-after.vbs: " & "AppendSlmgrLogfile()" & " an error occurred " & Err.Number)
Else
    Status = Utils.AppendLog("phase4-after.vbs: " & "AppendSlmgrLogfile()" & " successfully")
End If

End Function

Add new comment

Appending zac.log to ztoolkit.log

Written on 24 June 2014.

When a device is registered to a ZCM zone in phase2 of the ENGL Imaging Toolkit's build process, the registration log is saved in a file called c:\ztoolkit\zac.log.

For troubleshooting purposes it might be convenient to have this information in ztoolkit.log as well. This little vbscript, to be run in phase2-after.vbs, appends the zac.log to ztoolkit.log:

AppendZacLogfile()

Function AppendZacLogfile

on error resume next

Set FSO = CreateObject("Scripting.FileSystemObject").OpenTextFile("c:\ztoolkit\zac.log",1)
strZacLogging = FSO.ReadAll()
FSO.Close

Status = Utils.AppendLog("phase2-after.vbs: " & strZacLogging)

If Err.Number <> 0 then
    'MsgBox "An error occured in routine AppendZacLogfile()"
    Status = Utils.AppendLog("phase2-after.vbs: " & "AppendZacLogfile()" & " an error occurred " & Err.Number)
Else
    Status = Utils.AppendLog("phase2-after.vbs: " & "AppendZacLogfile()" & " successfully")
End If

End Function

Add new comment

Setting a bundle requirement for Windows bundles for virtual machines

Written on 24 June 2014.

Using this vbscript in one of the ENGL phase process 0,1 or 2, you can set a System Variable which reflects where you're working in a Virtual Machine:

IsVirtualMachine = Utils.IsVirtualMachine()

If IsVirtualMachine <> 0 Then
status = Utils.SetSystemEnvironmentVariable("VIRTUALMACHINE", "true")
Else
status = Utils.SetSystemEnvironmentVariable("VIRTUALMACHINE", "false")
End If

Then if you want to install e.g. VMware Tools in phase 3, only on Virtual Machines, you can add this requirement to the Windows bundle:

Environment Variable Value 'VIRTUALMACHINE' Equal to: true

Doing so, this Windows bundle will only be installed on virtual machines and will be skipped on physical machines.

Add new comment

Start
Prev
1
2
Next
End