Friday, June 03, 2011

Configmgr/SCCM, Abort PXE issue when attempting rebuilding a PC (re-run a TaskSequence)

Sometimes when attempting to re-image a system you can sometimes be greeted with an abortPXE error. This can even happen after you delete the record from SCCM. What's happening is the WDS/PXE service can be holding onto the record until the cache expires... this cache can sometimes take a long time to expire.

lucky for us since SCCM 2007 SP/2 We've been able to set the cache expiry from the registry.


On a x86 machine
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXEOn a x64 machine the registry key is under WOW6432NodeHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\SMS\PXECreate a new DWORD value CacheExpire, and set the desired value in seconds. For example, if you prefer the cache expired in 2 minutes, set the value to 120. If the value is set to 0, then the default 60 minutes value is used.
Note: Setting the value in CacheExpire is only supported in ConfigMgr 2007 SP2.

for more information see

http://blogs.technet.com/b/configmgrteam/archive/2010/05/27/pxe-cache-expire-behavior-in-configuration-manager-2007-sp1-and-sp2.aspx

Notes:
I found this can also happen if you delete the record from the system and the target computer is still on and operating before you shut it down. the client sends an update to SCCM before you shut it down.

Thursday, May 26, 2011

What's wrong with installing an MSI and a PATCH at the same time?

A few fellow SCCM Engineers have come across this issue. You're trying to install an MSI based application and apply a PATCH.msp at the same time. With SCCM this usually is met with error 1635 unable to locate the patch file. This happens because when you specify the patch the MSI installer doesn't know where the relative location of the patch file is (probably something  that M$ has to fix up at some point).

To get around this problem there are 3 general solutions..

1. Separate the install and patch process (i.e handle them in separate steps)
2. Specify the absolute path the to MSP (which can be difficult if you have multiple installer locations)
3. Create and admin point from the original software and then patch the admin point with the patch.msp. This way you don't have to patch anything when you install as the admin point has the updated files already.

Personally option 1 or 2 are the easiest for me.

More information is available on MSDN: [also you can see in the example they put the entire path.]
http://msdn.microsoft.com/en-us/library/aa370576(VS.85).aspx

Thursday, March 31, 2011

VBscript - How to obtain the local SCCM Proxy Point from WMI

Say you have an application you need to run from a share on local SCCM site server, not from a specific DP.

In this case it can be really easy to determine what your local site server is by querying local WMI for the MPProxy Point.


strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\ccm")
Set colItems = objWMIService.ExecQuery( _
"SELECT * FROM SMS_MPProxyInformation",,48)
For Each objItem in colItems
Wscript.Echo "sitename: " & objItem.name
Next

Thursday, March 24, 2011

SCCM - MSI Error 1603 error when deploying an application to a standard user.

I recently came across and issue whereby I created a deployable package and it worked fine under admin but kept failing on a users machine.

In the MSI log it would error out with

ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80070006
Exit code 1603

The application was deployed using and MSI and it was trying to start up the installscript engine but failed. It seems this application was meant to use a setup.exe to invoke the MSI.

the root cause of this turns out to be the InstallScript DCOM Permissions for any version of IISscript installed. We need to change the Installsheild permissions from executing as the 'interactive user' to executing as the 'Launching User'. this way when he MSI executes and calls the installscript service to start it will start up as the user who kicked off the installer, not as the logged on user (standard user) who doesn't have rights to install software.

AppDeploy have a good write up on this issue.

More info here:
Appdeploy forum
AppDeploy
AppDeploy
A good video here
Appdeploy Video - Dealing with InstallScript

Wednesday, February 09, 2011

SCCM collection Software not installed. Two methods same outcome.

I needed to quickly create a collection based on AppX not installed on workstations.

There are 2 ways achieve this;

1. Create a collection of PC's that have AppX installed then create a second collection excluding the installed.

OR

2. Do all the above in a single collection.

Both are acceptable answers and will lead you to same outcome. Step 1 will allow you to quickly report how many of 'AppX' is installed which might be handy to some.

I'll show you how to do both methods.

Method 1: Create 2 collections.

--Collection 1 determine the workstations that have APPX installed.
select
SMS_R_SYSTEM.ResourceID,
SMS_R_SYSTEM.ResourceType,
SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,
SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client

from SMS_R_System
where SMS_R_System.ResourceId
in
(select SMS_R_System.ResourceID
from SMS_R_System
inner join SMS_G_System_ADD_REMOVE_PROGRAMS
on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId
where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName
LIKE 'APPX%')


--Collection 2 shows clients not in first collection.
-- Also client must = 1
select
SMS_R_SYSTEM.ResourceID,
SMS_R_SYSTEM.ResourceType,
SMS_R_SYSTEM.Name,
SMS_R_SYSTEM.SMSUniqueIdentifier,
SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client
from SMS_R_System
where SMS_R_System.ResourceId not in
(select ResourceId from SMS_CM_RES_COLL_SSDXXXXX)
and SMS_R_System.Client = 1


Method 2: Create a single collection based query.
Base


select
SMS_R_System.ResourceID,
SMS_R_System.ResourceType,
SMS_R_System.Name,
SMS_R_System.SMSUniqueIdentifier,
SMS_R_System.ResourceDomainORWorkgroup,
SMS_R_System.Client
from SMS_R_System
inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId
where SMS_G_System_COMPUTER_SYSTEM.Name not in
(select distinct SMS_G_System_COMPUTER_SYSTEM.Name
from SMS_R_System
inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId
inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId
where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%AppX%")

Friday, January 28, 2011

PXE Error after booting - The certificate associated with this media has expired

Error: the certificate associated with this media has expired. New
Media with a valid certificate will need to be created.

If your boot media cert's have not expired then this is easy to fix as it will just be the PXE point that has expired.

1. Go to Site Database --> Site Management --> --> Site Settings --> Site Systems and choose the server where the PXE Service Point is located.

2.In the right pane, right click on the ConfigMgr PXE service point and choose Properties.

3. Click on the Database tab and locate the Create self-signed PXE certificate option.

4. Under Create self-signed PXE certificate, set the Set expiration date option to some time in the future.
5. Click OK.
6. Go to Site Database --> Site Management --> --> Site Settings --> Certificates --> PXE and verify that there is now a valid non-expired non-blocked Certificate.

This should fix up your issue.. However if your boot media Cert's have expired then you need to rebuild your boot images with new Cert's