Skip to main content

Posts

Showing posts with the label Scripts

SCCM DCM Symantec Backup Exec.Cloud

The intention this article is to provide an overview of DCM within SCCM and more importantly for some, the ability to create a baseline for Symantec Backup Exec.Cloud and generate a KPI. The DCM node within SCCM is made up of two parts Configuration Baselines and Configuration Items.  Right click on Configuration Items > New > Application configuration Item Identification: Provide a name and categor Detection Method: Select Use custom script (VBScript) Option Explicit                 If(IsNWMInstalled()) Then                 WScript.Echo("SymantexCloudBackup")                 End If                 Function IsNWMInstalled()          ...

SCCM DCM Symantec Backup Exec.Cloud

The intention this article is to provide an overview of DCM within SCCM and more importantly for some, the ability to create a baseline for Symantec Backup Exec.Cloud and generate a KPI. The DCM node within SCCM is made up of two parts Configuration Baselines and Configuration Items.  Right click on Configuration Items > New > Application configuration Item Identification: Provide a name and categor Detection Method: Select Use custom script (VBScript) Option Explicit                 If(IsNWMInstalled()) Then                 WScript.Echo("SymantexCloudBackup")                 End If                 Function IsNWMInstalled()       ...

SHA-1 checksums for files

To obtain the hash, you’ll need a utility that calculates SHA-1 checksums for files – fortunately Microsoft has a free download called the File Checksum Verifier Utility . Run fciv.exe from the command line on your reference PC to obtain the desired checksum:

SHA-1 checksums for files

To obtain the hash, you’ll need a utility that calculates SHA-1 checksums for files – fortunately Microsoft has a free download called the File Checksum Verifier Utility . Run fciv.exe from the command line on your reference PC to obtain the desired checksum:

NOMAD 1E not responding to a package status request

Overview : During a SCCM task sequence a specific application is to be installed.  The task sequence is designed to use a NOMAD cache to poll the source.  The sequence fails as no available cache is available. How to troubleshoot? On the NOMAD cacheing server Open regedit and check the package status details. Select the sub folder that corresponds to the cached item and review the details on the right.  You should check the following item are present and correct [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\1E\NomadBranch\PkgStatus\LDC002FE] "Percent"="100.000" "Version"="2" "CachePriority"="1" "CacheToFolder"="D:\\NomadBranchCache" "ReturnStatus"="Completed Successfully" "AlreadyCached"="0" Also check the logs for specific behaviour. C:\ProgramData\1E\NomadBranch\LogFiles The log should state "CacheStatus: (ELD)  pkgID="LDC002FE"(0) local=100.000% verified...

NOMAD 1E not responding to a package status request

Overview : During a SCCM task sequence a specific application is to be installed.  The task sequence is designed to use a NOMAD cache to poll the source.  The sequence fails as no available cache is available. How to troubleshoot? On the NOMAD cacheing server Open regedit and check the package status details. Select the sub folder that corresponds to the cached item and review the details on the right.  You should check the following item are present and correct [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\1E\NomadBranch\PkgStatus\LDC002FE] "Percent"="100.000" "Version"="2" "CachePriority"="1" "CacheToFolder"="D:\\NomadBranchCache" "ReturnStatus"="Completed Successfully" "AlreadyCached"="0" Also check the logs for specific behaviour. C:\ProgramData\1E\NomadBranch\LogFiles The log should state "CacheStatus: (ELD)  pkgID="LDC002FE"(0) local=100.000% verified...

How to sign a powershell script

How to sign a powershell script http://blogs.technet.com/b/heyscriptingguy/archive/2010/06/16/hey-scripting-guy-how-can-i-sign-windows-powershell-scripts-with-an-enterprise-windows-pki-part-1-of-2.aspx http://blogs.technet.com/b/heyscriptingguy/archive/2010/06/17/hey-scripting-guy-how-can-i-sign-windows-powershell-scripts-with-an-enterprise-windows-pki-part-2-of-2.aspx $cert=(dir cert:currentuser\my\ -CodeSigningCert) Set-AuthenticodeSignature demoscript2.ps1 $cert -TimestampServer  http://timestamp.comodoca.com/authenticode My PKI root is called  pki.harper.labs , and it is already trusted by my domain members, as shown in the following image. I will follow these steps: Make the code signing certificate template available on my issuing certificate server. Request a code signing certificate for my user. Sign my Windows PowerShell script and run it. Deploy the code signing certificate as a trusted publisher through Active Directory. Step 1: Make the code signing certificate temp...