Get ConfigMgr Versions

Just a quick blog to share a little SQL query that shows what version of ConfigMgr is being used at each site in you hierarchy.

SELECT DISTINCT SiteServer,’Site Version Number’ = Version,’Version Name’=
CASE
WHEN Version = ‘4.00.5135.0000’ THEN ‘ConfigMgr 2007 Beta 1’
WHEN Version = ‘4.00.5931.0000’ THEN ‘ConfigMgr 2007 RTM’
WHEN Version = ‘4.00.6221.1000’ THEN ‘ConfigMgr 2007 SP1’
WHEN Version = ‘4.00.6221.1193’ THEN ‘ConfigMgr 2007 SP1 with KB977203’
WHEN Version = ‘4.00.6487.2000’ THEN ‘ConfigMgr 2007 SP2’
WHEN Version = ‘4.00.6487.2111’ THEN ‘ConfigMgr 2007 SP2 with KB977203’
WHEN Version = ‘4.00.6487.2157’ THEN ‘ConfigMgr 2007 R3’
WHEN Version = ‘4.00.6487.2207’ THEN ‘ConfigMgr 2007 R3 with KB2750782’
WHEN Version = ‘5.00.7561.0000’ THEN ‘ConfigMgr 2012 Beta 2’
WHEN Version = ‘5.00.7678.0000’ THEN ‘ConfigMgr 2012 RC1’
WHEN Version = ‘5.00.7703.0000’ THEN ‘ConfigMgr 2012 RC2’
WHEN Version = ‘5.00.7711.0000’ THEN ‘ConfigMgr 2012 RTM’
WHEN Version = ‘5.00.7711.0200’ THEN ‘ConfigMgr 2012 RTM CU1’
WHEN Version = ‘5.00.7711.0301’ THEN ‘ConfigMgr 2012 RTM CU2’
WHEN Version = ‘5.00.7782.1000’ THEN ‘ConfigMgr 2012 SP1 Beta’
WHEN Version = ‘5.00.7804.1000’ THEN ‘ConfigMgr 2012 SP1’
WHEN Version = ‘5.00.7804.1202’ THEN ‘ConfigMgr 2012 SP1 CU1’
WHEN Version = ‘5.00.7804.1300’ THEN ‘ConfigMgr 2012 SP1 CU2’
WHEN Version = ‘5.00.7804.1400’ THEN ‘ConfigMgr 2012 SP1 CU3’
WHEN Version = ‘5.00.7804.1500’ THEN ‘ConfigMgr 2012 SP1 CU4’
WHEN Version = ‘5.00.7804.1600’ THEN ‘ConfigMgr 2012 SP1 CU5’
WHEN Version = ‘5.00.7958.1000’ THEN ‘ConfigMgr 2012 R2’
WHEN Version = ‘5.00.7958.1101’ THEN ‘ConfigMgr 2012 R2’
WHEN Version = ‘5.00.7958.1203’ THEN ‘ConfigMgr 2012 R2 CU1’
WHEN Version = ‘5.00.7958.1303’ THEN ‘ConfigMgr 2012 R2 CU2’
WHEN Version = ‘5.00.7958.1401’ THEN ‘ConfigMgr 2012 R2 CU3’
WHEN Version = ‘5.00.7958.1501’ THEN ‘ConfigMgr 2012 R2 CU4’
ELSE ‘Unknown version’
End
FROM Sites

The version information came from http://en.wikipedia.org/wiki/System_Center_Configuration_Manager

, , , ,

Leave a comment

Registering existing Nomad Cache in ActiveEfficiency Single Site Download (SSD)

This is a continuation of the conversation I have with a customer that was started in my previous blog ‘How to enable the Nomad Single Site Download (SSD) feature after deployment of Nomad

Customer question: ‘As you know we have been using Nomad for months now and have a large amount of content cached on clients, is it possible to tell Nomad to populate ActiveEfficiency?’
Answer: ‘Sorry there is no Supported way to do this.’

Customer: ‘OK, but is it possible?’
Answer: ‘Yes, if you follow this process but remember this will not be supported by 1E’

As this process is not supported by 1E the following disclaimer applies

DISCLAIMER

Use of these items and process is at your sole risk.
All items and information are provided “as-is”, without any warranty, whether express or implied, of accuracy, completeness, fitness for a particular purpose, title or non-infringement. In no event shall 1E, its suppliers or author of this blog be liable for any damages whatsoever including direct, indirect, special, incidental or consequential, loss of business profits or special damages, even if 1E, its suppliers or author of this blog have been advised of the possibility of such damages.

I highly advise that you complete this process in a lab environment and fully understand the process before attempting the steps in production. Remember this is an unsupported process.

Step one – Stop Nomad Branch service to prevent the Nomad service responding to subnet election requests.
Example Powershell code: Stop-Service NomadBranch

Step two – Delete the Nomad Branch cache package status reference from the registry, this will force Nomad to enter Recovery mode when it next starts up.
Example Powershell code: Remove-Item -Path HKLM:\Software\1E\NomadBranch\PkgStatus -Recurse

Step three – Start Nomad Branch service, in the NomadBranch.log you should see

1
and the registry will show.

2
Example Powershell code:
Start-Service NomadBranch

Step four – Finally, to finish the reactivation process execute NomadBranch.exe -ActivateAll. This will complete the activation process.

3
and the registry will show.

4
Example Powershell code:
NomadBranch.exe -ActivateAll

Note: Using this process to populate the ActiveEfficiency database may affect some of the 1E Nomad reports.

Below is an example Powershell script that can enable SSD and register the content of the Nomad Cache with ActiveEfficiency

Final warning remember this is an unsupported process

#<DNS Alias for ActiveEfficiency Server>
$AEServerDNSAlias = ‘ActiveEfficiency’

# 0 is disabled, 1 is enabled to read from AE, 2 is enabled to write to AE 3 is enabled for both read and write.
$SSDEnabled = ‘3’

#Change to HK:M:\Software\WOW6432Node\1E\NomadBranch if 32 bit Nomad agent is used on 64 bit OS with CM2007 client
$RegPath = ‘HKLM:\Software\1E\NomadBranch’

#Stop Nomas service so that it does not respond to elections
Stop-Service NomadBranch

#Enable SSD
Set-ItemProperty -Path $RegPath -Name SSDEnabled -Value $SSDEnabled -Force

#Set ActiveEfficiency URL
Set-ItemProperty -Path $RegPath\ActiveEfficiency -Name PlatformURL -Value http://$AEServerDNSAlias/ActiveEfficiency -Force

#Delete all Package Status register key
Remove-Item -Path $RegPath\PkgStatus -Recurse

#Restart Nomad to allow Nomad to register into 1E ActiveEfficiency
Start-Service NomadBranch

#Finally reactivate the Nomad cache so that it shows as 100% complete rather that 99.00%
NomadBranch.exe -ActivateAll

, , , ,

Leave a comment

How to enable the Nomad Single Site Download (SSD) feature after deployment of Nomad.

I was recently asked by a customer how to enable the Nomad Single Site Download (SSD) feature, they had been using Nomad for some time but had never implemented ActiveEfficiency.

Step one – Install ActiveEfficiency server by following the ActiveEfficiency installation guide that ships with the ActiveEfficiency or 1E ActiveEfficiency online help.
Note: It is good practice to create a DNS alias for the ActiveEfficiency server.

Step two – Create the SSD location map using the sample PostADSiteandSubnet.ps1 Powershell script shipped with Nomad. This will query Active Directory Sites and Services and populate the Location table (if the information in AD Sites and Services does not represent your geographical locations then a custom script should be used).

Step three – Enable SSD on all Nomad agent

Change the HKLM\Software\1E\NomadBranch SSDEnabled to 3, this allow the SSD feature to both publish and consume information from ActiveEfficiency.

Change HKLM\Software\1E\NomadBranch\ActiveEfficiency PlatformURL to http:// /ActiveEfficiency

Example Powershell code to set both of these values:

Set-ItemProperty -Path HKLM:\Software\1E\NomadBranch -Name SSDEnabled -Value 3 –Force

Set-ItemProperty -Path HKLM:\Software\1E\NomadBranch\ActiveEfficiency  -Name PlatformURL -Value http:// /ActiveEfficiency –Force

Not much to it, the next package that is downloaded via Nomad will register in the ActiveEfficiency database and will be available for all clients on associated subnets.

Note: Nomad will always hold a local subnet election before using the SSD feature.

In my next blog I’ll look at populating ActiveEfficiency with SSD information for software already in the Nomad Cache.

1 Comment

Comparing Trace32/CMTrace and CMLogViewer from System Center Support Center

As a long time ConfigMgr admin and now 1E Consultant I have been using Trace32 and CMTrace for longer than I care to remember. Both tools have made reading ConfigMgr log file so much easier (sorry Wally, I know you are a Notepad fan) and most of my scripts will format their log file output in the same format so that if I need to I can merge the logs.

Even though these log viewer are great they have a few limitations:

  • you can only highlight on one string at a time
  • you can only filter on one string at a time
  • the default when setting the filter is ‘is equal to’ (lost count how many times I’ve had to go back a change this after applying)
  • No shortcut key to select either filter or highlight

Still even with these limitation both tools have been used by sysadmins the world over for many years.

In September Microsoft released System Center Support Center (which can be downloaded here) which include a new improved log file viewer called ‘Support Center Log Viewer’ the exe is CMLogViewer.exe. In my opinion this has addressed all of the limitation the previous viewers had, mainly by including a ribbon with all the option available at a click of a button.

Here are my favourite features:

  • Quick filter – simply start typing a word and after each key press the log view is refreshed
  • Open log in current view – open new log file and merge with current log file
  • Advanced filter – this allow for multiple include, excludes and highlights(with multiple colours).

Best of all the filters can be saved and loaded giving the ability to create and share filter files to help troubleshooting.

I highly recommend that you give the new log viewer a go.

, ,

Leave a comment

Renaming local accounts during Windows 7 build

I was recently helping a customer optimise their Window 7 Task Sequence and found a step called Rename Accounts that was taking 8 or 9 minutes to complete. This seemed to be excessive, on investigate the step was running a 25 line vbs script that would basically swap the Administrator account name with another account using WMI Query to find the account eg Select * from Win32_UserAccount where LocalAccount = True and Name = ‘Administrator’.

Running this query directly from WBEMTEST result in a wait of over 2 minutes as it appears queries the domain for all counts.

By simply changing the where statement to Where Domain = “<Computer Name>” and Name = “Administrator” the query runs in seconds.

This is an example of how this can be handle in the script.

Set wshShell = CreateObject(“WScript.Shell”)
Set objWMIService = GetObject(“winmgmts:\\” & strComputerName & “\root\cimv2”)

strcomputername = wshShell.ExpandEnvironmentStrings (“%COMPUTERNAME%”)

Set colAccount = objWMIService.ExecQuery (“select * from Win32_UserAccount where Domain = ‘” & strComputerName & “‘ and Name = ‘Administrator'”)
For Each objAccount in colAccount
     wscript.echo objAccount.name
Next

 

Alternatively it is possible to use the Wscript.Network object as shown below.

Set objNetwork = CreateObject(“Wscript.Network”)

strComputer = ucase (objNetwork.ComputerName)

Set objComputer = GetObject(“WinNT://” & strComputerName)

Set objUser = GetObject(“WinNT://” & strComputerName & “/<OldUserName>/User”)

objComputer.MoveHere objUser.ADsPath,”<NewUserName>”

Note: all values inside <  > should be replaced with the actual value and should not include the < > characters.

 

 

,

2 Comments

ConfigMgr 2012 console crash while editing application

SCENARIO:

“I tried to edit one application and the console crashed and now the application is in read only mode. (The object will be unavailable)

How do I unlock this object?

Should I use PowerShell script or there is another solution for that? I have only one primary.”

Cause:

The console is a SEDO-enabled object.

The console crash creates an explicit lock on the console object and there is a built-in 30 minute timer controlling how long an object will remained locked.

Solution(s)

  • Wait a while and try again after the timer expires (L)
  • Use SQL:

Select * from SEDO_LockState where LockStateId=1

Update SEDO_LockState set LockStateID=0 where LockStateID=1

More details on the root cause may be found here http://cm12sdk.net/?p=806 & http://cm12sdk.net/?p=777

Leave a comment

Understanding Nomad Peer Backup Assistant (PBA) log files.

With the introduction of Nomad Migration Data Sharing into Nomad 4.1 (now known as Peer Backup Assistant (PBA)) I thought it would be a good time to investigate how Nomad Branch service logged the communication between all NMDS enabled clients on a subnet.

For simplicity I decided to start with only use two devices and using NMDS in standalone mode rather than include USMT.

I hope to follow this article with different scenarios include using NMDS with USMT.

Below are two tables containing a time line of commands executed, the output from each client’s Nomad Branch log file and notes to explain what is happening during normal NMDS process. The first details NMDS saving data to another Nomad client and the second is how to restore & delete the data.

Notes are in BLUE

Commands are in GREEN

Log information is in BLACK

Saving data with PBA

Nomad Agent requesting storage (NOMAD-Cli1)

Nomad Agent responding to storage request (NOMAD-Cli3)

This command is used to broadcast a request for storage space on another NMDS enable Nomad Branch computer. In my lab NOMAD-Cli3 has NMDS enabled and will respond to the request for storage.

Command line: NomadBranch.exe -NMDSPOLL,A,10

Connect 00000000 00000000 01617838

NMDS_Thread started

Bcasting NMDS_Poll ID=”A” reqd=10 1E01000A-7

Nomad sends out a broadcast requesting 10MB of storage for request named A.

NMDS_Poll from NOMAD-Cli1 10.0.1.30:65091 for ID=”A” 0.000% (0)

Nomad receives the broadcast and starts a thread to process the request

NMDS_Thread started

NMDS: Reserved=10 (10 out of 1024)

Nomad is able to fulfil request an reserves 10MB of the configured 1GB

Sending NMDS_Offer ID=”A” to 10.0.1.30:1779 59.084%

Nomad sends a reply to the requesting computer NOMAD-CLI1 with an offer of space

NMDS_offer from NOMAD-Cli3 10.0.1.32:62215 for ID=”A” 59.084%

Nomad receives the offer from NOMAD-CLI3

Sending NMDS_Accept ID=”A” to NOMAD-Cli3 10.0.1.32:1779

As NOMAD-CLI1 only receives 1 offer it will accept it and sends an acceptance to NOMAD-CLI3

NMDS_accept from NOMAD-Cli1 10.0.1.30:51596 for ID=”A” 0.000% (0)

Nomad receives the acceptance and will create a folder and share this with a unique name

Sharing D:\…..\…..\NMDS\A as NomadNMDS0001 uses=1

Sending NMDS_Confirm ID=”A” \\NOMAD-Cli3\NomadNMDS0001
to 10.0.1.30:1779

Nomad sends a confirmation that the share has been created to NOMOAD_CLI1

NMDS_confirm from NOMAD-Cli3 10.0.1.32:62215 for ID=”A” 0.000% (0)

Nomad receives the confirmation from NOMAD-CLI3

Confirmed MachName=NOMAD-Cli3

Disconnected

As this example is using standalone NMDS we copy some file over into the NMDS share on the Nomad-Cli3

Command line: xcopy <some files> \\Nomad-Cli3\NomadNMDS0001\

Once all files have been copied the NMDS session needs to be complete, this will register that no more data will be copied to this share. Nomad will set the automatic deletion of the data to 7 days in the future.

Command line: NomadBranch.exe -NDMS_COMPLETE,A

Connect

Completeing “A”

Sending NMDS_complete ID=”A” to 10.0.1.32:1779

Nomad send a complete instruction to NOMAD-CLI3 for request named A

NMDS_complete from NOMAD-Cli1 10.0.1.30:51596 for ID=”A” 0.000% (0)

Nomad receives the complete instruction

Completed “A” – valid until xxxxx

Disconnected

Removed A from list

When data needs to be restored from PBA store

The first action is to find the share on the network this is done using the NDMS_FIND switch with the request ID that was originally used

Command line: NomadBranch.exe -NDMS_FIND,A

Connect

NMDS_Thread started

Bcasting NMDS_find ID=”A” reqd=0 1E01000A-10

Nomad sends out a broadcast requesting to find the computer with the data from request named A.

NMDS_find from NOMAD-Cli1 10.0.1.30:65091
for ID=”A” 0.000% (0)

Nomad receive the request for information because it has the required data it will respond with a confirmation message which includes the share name to use

Sending NMDS_Confirm ID=”A” \\NOMAD-Cli3\NomadNMDS0001 to 10.0.1.30:1779

NMDS_confirm from NOMAD-Cli3 10.0.1.32:62215 for ID=”A” 0.000% (0)

Nomad receives the confirmation from NOMAD-CLI3

Confirmed MachName=NOMAD-Cli3

Disconnected

Transfer files from NMDS back to a location on NOMAD-CLI1

Command line: xcopy \\Nomad-Cli3\NomadNMDS0001\*.* <location to restore to>

Once all the data has been successfully copied back and the data is no longer required it can be removed from the host. Note if this command is not used then the data would be delete automatically after a defined amount of time

Command line: NomadBranch.exe -NDMS_DELETE,A

Connect

Deleteing “A”

Sending NMDS_delete ID=”A” to 10.0.1.32:1779

Nomad sends a delete instruction to NOMAD-CLI3 to delete the data for request named A

NMDS_delete from NOMAD-Cli1 10.0.1.30:51596 for ID=”A” 0.000% (0)

Nomad receive the request to delete NMDS data for request named A

Sending NMDS_Confirm ID=”A” \\NOMAD-Cli3\NomadNMDS0001 to 10.0.1.30:51596

Nomad sends a confirmation to NOMAD-CLI1 that it has received the request to delete data

Disconnected

Deleteing “A” \\.\NomadNMDS0001

Nomad deletes the data from share

Share NomadNMDS0001 deleted

Nomad deletes the share

Delete User NomadNMDS0001

Nomad deletes the local user that was created the access the
share

INFO: Deleting D:\….\….\NMDS\A

Nomad deletes the folder from the file system

Released=10 (0 out of 1024)

Finally Nomad will remove the reservation for 10MB from its cache

regrecurdel

NMDS_Thread exits

NMDS_Thread exits

Removed A from list

, ,

Leave a comment