Tag Archives: sccm

IT

Intel ATM and SCCM

Leave a comment

I hate this. I can’t figure out how it works. It will install fine sometimes, and then not others. So far, after various amounts of fiddling I think I have it running. You’ll get the odd error messages, kerberos authentication will randomly work or not… But I think I’m in a happy place now.

Anyway, I plan to add error messages to this post that you may hit. So far, I’ve modified the task sequence so that error 42 is considered a success. This just indicates it didn’t have permission to save the log file for whatever reason. Another one I’ve seen is:
(0xc0002823). Call to function failed. DNS name does not exist. (0xc0000018)
The error code at the end actually means the exact opposite and that there are two IP addresses in DNS for this computer. This happens with us as people often connect via VPN which is in a different range. Delete the offending IP from DNS and try it again.

IT, windows

SCCM OSD 80004005

Leave a comment

I’ve been having a lot of trouble recently with this error. Running an OSD from PXE results in the error 80004005. Nothing specific in the logs other than that error message. I noticed tat if I disabled the install drivers part of the TS, then it worked ok. So clearly one of the drivers was a mess. After a lot of searching I found an article that basically said it was due to the entwork drivers. Now, WinPE includes network drivers, and if this drive is different to the one used by Windows itself, when the driver is updated it will cause a disconnection from the DP. This causes the error. The way around that I have found is to make the advertisement download the content lcoally. This means that it won’t disconnect from the DP, as it’s running locally. Why this is a problem I don’t know. Surely it should jsut try to connect again, but I guess not.

There is an article here on Windows Noob (very good site) http://www.windows-noob.com/forums/index.php?/topic/1688-nic-devices-that-require-a-special-driver-for-winpe-may-cause-a-configmgr-task-sequence-to-fail/ that explains it a bit more

Stuff

Office 2010 Rollout Fun

Leave a comment

I’ve been attempting to install office 2010 to several PCs using SCCM 2007 (sp2, r3). What a pain. You’d think deploying the exe with an appropriate config.xml would be ok, but it seems to ahve serious issues upgrading older versions. Originally, 2010 was deployed sans outlook as we’er a Notes house, however, Outlook is being deployed at one site so I create an MSP that would modify it, using setup.exe /admin. Easy enough. This worked on most of the computers, but some of them it managed to wreck.

Found [0] resource files under the default folder.
Resource File Manager : Current user’s LCID is [2057].
Resource File Manager : error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-GB].
Unable to locate a suitable resource file which contains resources that match the current user’s Locale [2057].

Found [0] resource files under the default folder.Resource File Manager : Current user’s LCID is [2057].Resource File Manager : error : ResourceFileManager does not contain at least one ResourceFile. Unable to find best match ResourceFile for CultureTag=[en-GB].Unable to locate a suitable resource file which contains resources that match the current user’s Locale [2057].

‘Setup Error’, Message: ‘The language of this installation package is not supported by your system.

Occasionally, setup would just reboot the machine when I tried to modify it. I couldn’t run it, I could’t manually use /uninstall either.

This is a UK machine with UK location and UK office. I’ve no idea waht the problem is, but I managed to sort it out with a combination of running the office 2010 uninstall tool which is here . I uninstalled everything that was remotely “officey” from ARP including the compatibility tools, ran every uninstall utility in the mentioned site and finally got it working.

As far as I can tell, something installed previously thought it was a finny language, though I’ve no idea what or why.

This has been an utter pain, and I’m very worried about deploying it company wide if it is this picky. Got it fixed eventually with the steps listed above though.

Good luck!

Stuff

SCCM Pre-R3 client patch

Leave a comment

Here’s my collection to deploy the “power management” pack to clients. This is the MSP file that you get with R3 that clients need to have in order to manage power settings correctly. This collection selection should work, at least it seems to do so anyway!

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientType = 1 and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Name = “SmsPowerManagement” and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < “4.0.6487.2157”

Stuff

SCCM SP2 Client Collection

Leave a comment

Looking for a way of deploying and updating the SCCM SP2 client to old clients? Well, here is the collection I’ve been using. This will list all the clients that are not running Service Pack 2.

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_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.ClientType = 1 and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Name = “CcmFramework” and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version < “4.0.6487.2000”