Trevor Sullivan

It could possibly be due to a difference in the mass storage driver that WinPE is using and the one being used in the full OS. Have you embedded the appropriate AHCI driver into your WinPE boot image? Make sure the driver versions used in your full Windows OS and WinPE are the same. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Try enabling the "Allow users to interact with this program" checkbox and see what happens. For the sake of making testing easier, you could publish this as an optional advertisement and execute it on-demand from Run Advertised Programs. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hello Chris, If you run powershell.exe with no parameters, it should start an interactive session which will never exit. This is probably not what you want ultimately. For testing purposes, open a cmd prompt and test your command in that before deploying through SCCM. For example, on a problematic 32-bit machine, open cmd, run powershell, and if it exits immediately, run "echo %ERRORLEVEL%" in the cmd prompt, and see what you get in return. It's possible that this will spit out the same error code you're seeing. Either way though, as I said above, it *should* start an interactive session, so I'd avoid deploying a straight "powershell.exe" command via SCCM. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Are your A records in DNS correctly resolving to your clients? I'd suggest spot-checking a few. Also, did you define a client push installation account that has administrative remote access to your client systems? By the way, you said that the "Client" column says "YES" -- this would mean the client is already installed, and does not need to be pushed. I'm a little confused why you're trying to push to existing clients. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Sorry, I should have clarified on that. You can use the built-in wbemtest.exe in Windows. 1. Open wbemtest.exe (and click Asynchronous) 2. Connect to the root\sms\site_abc WMI namespace 3. Hit "Enum Instances" 4. Type "SMS_R_System" in the class name field 5. Randomly double-click a few instances in the list returned and examine the value of the SystemGroupName property Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

I couldn't say for sure, but I would guess that maybe it's a console bug? Try the PowerShell code next time and see if it disappears. That code I posted only deleted the first resource returned with that name, so if there are multiple resources, you may need to run it repeatedly. Alternatively, try this: Get-WmiObject -Class SMS_R_System -Namespace root\sms\site_lab -Filter "Name = 'SCCMCLIENT01'" | % { $_.Delete() } Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You're quite welcome Glad it got worked out. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Yes, if the client deployment / assignment process is working, you should be able to safely overlook this error. I have a feeling that the site server is attempting to make a connection to the remote system's root\ccm WMI namespace (exists only if the SCCM client is installed). Assuming this is true, it probably does this as a check to ensure that the client is not already installed (but perhaps unassigned or broken). Just a theory, but seems probable ... Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Check out the Microsoft Deployment Toolkit (MDT) 2010 Update 1 -- this has everything you need to get started (including documentation). Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Looks like the management point is functioning alright, but the distribution point is not working. Can you access the SMSPXEIMAGE$ and standard package share from another Windows computer? Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

So create multiple task sequences with only one or two steps as necessary, and advertise multiple sequences. You can even have a conditional on the task sequence items (or create a group and set the condition there), that detects if the machine needs to be rebooted or not. Allow the user to run these task sequences as necessary via Run Advertised Programs (make them optional advertisements). Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Can you just shutdown the SCCM server and bring it back up after the upgrade (not sure what might change during the upgrade, since you didn't specify exactly what upgrade is happening -- OS, service pack, SQL version?) Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Typically, to do anything cross-forest, you would need to establish a trust between them. In SCCM 2012, you can add a forest to the list of forests, and specify alternate credentials to use for that forest (publishing to AD, discover sites / subnets). Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

1. As of Beta 2, there is no Mac OS client 2. When it's done Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Just delete the resource out of the console. It won't be marked as inactive until a certain time period after the client has not reported in. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You can also build a task sequence to install your application, and then set the appropriate conditionals on each task sequence item. This is a powerful, flexible, and easy method of deploying applications, which is used by many ConfigMgr folks out there. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You have to create a site boundary group and assign your slow site boundaries to it. In the "Properties" window of the boundary group you are working with, click the "References" tab, select the distribution point under "Content Location" that you want to change to a slow link, and then hit "Change Connection" button. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

This link should help you find the appropriate parameters to pass to the SP1 installer. Create a batch file and test out the silent installation on a machine manually before deploying it through SCCM, to save yourself time during testing. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

I would strongly recommend against doing what you did -- modifying the ConfigMgr database directly can have unexpected results. The proper way to delete a resource would be to remove it through the SCCM WMI provider: Here's a PowerShell script that should delete it for you: $SccmResource = @(Get-WmiObject -Class SMS_R_System -Namespace root\sms\site_lab -Filter "Name = 'SCCMCLIENT01'")[0] $SccmResource.Delete() Replace "lab" with your three-digit site code, and replace "SCCMCLIENT01" with the target client name. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Do you have multiple languages of Office 2010? My understanding is that you have to have SP1 packages available for all proofing tools languages installed on a Office 2010 installation. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Run everything through a task sequence and set your conditionals on each individual task sequence item. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

SCCM doesn't create GPOs, and you should be careful that whatever GPOs you do create are not interfering with proper operation of SCCM services. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Hey there Adam, I'd strongly recommend using Desired Configuration Management (DCM) for this purpose. That way, you don't have to go around extending hardware inventory needlessly. Do you need specific help with building a DCM compliance rule for this? Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

You mentioned the sitectrl.log was getting modified ... I'd check that out, since the Site Control File (SCF) controls SCCM site roles (such as the PXE Service Point deployment). Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86

Use a WMI browser on your SCCM primary site to pull a list of SMS_R_System instances, and examine the SystemGroupName property on them. This should tell you if nested group information is getting pulled or not. I suppose I wouldn't be surprised if the discovery method were not pulling nested group info. Hope this helps. Cheers, Trevor Sullivan http://trevorsullivan.net http://twitter.com/pcgeek86