Archive

Archive for the ‘ConfigMgr2007’ Category

Use WSUS Server for updating Windows 7 in OSD.

March 22nd, 2011 ravnda No comments

Don’t wanna use SCCM 2007 to update Windows? But need to update Windows Image in OS Deployment.

Here is one way to do it with MDT 2010:

 

1. Update Customsettings.ini with this line: ( Change it to your WSUS Server.)

WSUSServer=http://InternalWSUSserver:port

2. Add this as a commandline in Task Sequence:

Use Toolkit Package

3. Add this as a commandline in Task Sequence:

Gather ( Use Customsettings )

4. Add this as a commandline in Task Sequence:

cscript.exe %deployroot%\scripts\ZTIWindowsUpdate.wsf

Now Windows 7 will be updated with the latest patches from your internal WSUS.

 

NB: For this to work your computer may have to be in the same domain as the WSUS server.

Categories: ConfigMgr2007 Tags:

Start a Configmgr 2007 program with powershell.

March 11th, 2011 ravnda No comments

Tried to start a ConfigMgr Program with Powershell? Then you are lucky.

Here you go:

 

  1. ErrorActionPreference = "SilentlyContinue"
  2.  
  3. ##################################
  4. #        Start a advertised program with powershell.                #
  5. #                                            #
  6. #        Date: 11.06.2010                            #
  7. #        Written by Stian Ravndal                        #
  8. #        Version: 0.6.5                                #
  9. ##################################
  10.  
  11. if ($args[0] -eq "-r")
  12. {
  13. #Reading variables from registry.
  14. $parameter1 = $args[1]
  15. $registry = Get-ItemProperty "HKCU:\Software\Atea\StartApp\$parameter1"
  16.  
  17. $programID = $registry.ProgramID
  18. $PackageID = $registry.PackageID
  19. }
  20. elseif ($args[0] -eq "-s")
  21. {
  22. # Variables is inserted from parameters.
  23. $programID = $args[1]
  24. $PackageID = $args[2]
  25. }
  26. else
  27. {
  28. # This will run if no parameters are specified.
  29. # Variables inserted in script.
  30. # Package ID from ConfigMgr.
  31. $PackageID = ""
  32.  
  33. # ConfigMgr ProgramID.
  34. $programID = ""
  35. }
  36.  
  37. function startapp
  38. {
  39. param ($programID, $PackageID)
  40.  
  41. if ($programID -eq "" -OR $PackageID -eq "")
  42. {
  43. [System.Windows.Forms.MessageBox]::Show("Something wrong with parameters.")
  44. return
  45. }
  46. else
  47. {
  48. }
  49.  
  50. $startapp = New-Object -ComObject UIResource.UIResourceMgr
  51.  
  52. if ($startapp -eq $null)
  53. {
  54. [System.Windows.Forms.MessageBox]::Show("CCM client not installed.")
  55. return
  56. }
  57. if ($startapp.IsMandatoryProgramPending() -eq "1")
  58. {
  59. [System.Windows.Forms.MessageBox]::Show("There is allready something running.")
  60. return
  61. }
  62. $program = $startapp.GetProgram($programID,$PackageID)
  63. if ($program -eq $null)
  64. {
  65. [System.Windows.Forms.MessageBox]::Show("You do not have access to this program.")
  66. return
  67. }
  68. $startapp.ExecuteProgram($programID, $PackageID,"")
  69. }
  70.  
  71. startapp $programID $PackageID

Download Script

Categories: ConfigMgr2007, Powershell Tags:

KB977203 won’t install on client.

March 10th, 2011 ravnda No comments

After you have installed the KB977384 on Configuration Manager 2007, the KB977203 won’t install at all, so don’t even try. =)

If you still have problems described in article 977203, the steps that involve CCMcertFix is still valid.

Description of the prerequisite hotfix for System Center Configuration Manager 2007 R3:
http://support.microsoft.com/kb/977384

User state migration is unsuccessful on a SCCM 2007 SP1 client or on a SCCM 2007 SP2 client after you install security update 974571:
http://support.microsoft.com/kb/977203

Categories: ConfigMgr2007 Tags: