Peter33

Make sure that you at least install the network driver and the storage driver for the machine type. CLibSMSMessageWinHttpTransport::Send: URL: MSCCM.domain.com:80 CCM_POST /ccm_system/request TSManager 12/7/2012 2:32:19 PM 1584 (0x0630) Error. Received 0x80072ee7 from WinHttpSendRequest. TSManager 12/7/2012 2:32:19 PM 1584 (0x0630) unknown host (gethostbyname failed) TSManager 12/7/2012 2:32:19 PM 1584 (0x0630)

I doubt that you certificate has expired already. The PXE cert runs for 1 year if you are using the default values. Make sure the system time is set correctly on your VM host computer. Alo in your VM, which should be received from the host anyways. The PXE certificate can be renewed in the PXE tab of the distribution point role properties.

Did you configure the NIC of your VM as bridged network?

Simply create a memebrship rule on your collection which queries the AD group membership. 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.SystemGroupName = "DOMAIN\\GROUPNAME" and SMS_R_System.Client = 1 and SMS_R_System.Obsolete = 0

You need to use a gather and a configure step in your task sequence to apply the settings to the local unattended.xml.

try to use "net stop" to stop the service.

Did you check the permissions on the SQL instance?

I got it running without any issues too. Server 2012, SQL 2012 CU3. WSUS is running on the same instance as SCCM. (of course not WID) The application catalog is working too. Just make sure you got all IIS prereqs installed.

Use PERCENTDISKSPACE instead of PERCENTFREEDISKSPACE. Edit: OK, just tested both parameters, PERCENTDISKSPACE and PERCENTFREEDISKSPACE. They work as expected, but only for fresh installations. So for client repairs they will not be applied but neither produce an error. Just uninstall the client on the machine and reboot. Then try again, rather with a client push installation.

HI james, This is a general error with no specific meaning. Post your smsts.log file for some detailed informations. If your task sequence does not start at all it's probably because you have not the correct NIC driver injected to your boot wim, or your distribution point is missing a package that is referred in your task sequence.

Also add as last line "exit /b %errorlevel%". This will return the exit code of the setup to the client.

No, SCCM is not a live monitoring system. You need to script this or use some 3rd party tool.

Actually i am formatting drive c: first. Then i create a new directory c:\hpbios and copy everything from the package to this directory. The run command in the task sequence holds the whole path "c:\hpbios\hp.cmd" (without cmd /c). Also, i recommend always to use a "pushd %~dp0" as first line, and "popd" as last line, in a batch file. This way your sources will be found in any case. Otherwise the instance will start in the home path of the user who is running the command (system32 as local system). I am using this method because i am also updating the BIOS and don't want to brick the machine by a failing network connection. After all si done the drive gets formatted again to have a clean starting point.

edit: obsolete post.

OK, they might be just entries of failed OS deployments? You have to manually delete them though.

These are unsuccessful PXE boot attempts, probably by machines which have PXE as first boot device, but are not covering a PXE deployment. You can't push a client to these objects. Just delete them and consider a change of the boot order.

You cant chose an "install software" step during the PE phase. Put the command line for the HP tool into a batch file. Don't create a program in your package. In your task sequence add a "run command line step" and call the batch file this way.

Well, it works for me. And i am using MDT too. Maybe it matters that i have configured the client push parameters on every single site, but i doubt it.

The GPO setting is correct. Verify your steps for the certificate. Here is a good guide.

Yes, its recommended to create a new package by definition. Then just replace the command line.

Have you applied the GPO setting to trust 3rd party updates, and installed the SCUP certificate on your clients?

Edit the command line in your client package. CCMSETUP.EXE /mp:SERVER SMSSITECODE=XXX /noservice FSP=SERVER SMSCACHESIZE=20000

You have probably a GPO that prevents the user from running regedit.exe. Use the "reg add" command instead, or a simple powershell script. md "HKCU:\Software\Test01" -force | out-null New-ItemProperty ("HKCU:\Software\Test01") -name "testentry" -value "myvallue" -type STRING -Force -ErrorAction SilentlyContinue | out-null

You need to extend your hardware inventory for the following registry entries first. They are all dword values. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\DomainProfile]"EnableFirewall" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\PublicProfile]"EnableFirewall" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\StandardProfile]"EnableFirewall"

No, you can't exclude them based on the advertisement (deployment). Just define a new collection, with the limiting collection you originally wanted to use, and create a new exclusion rule for it. Of course you could also define a custom requirement rule in your application which excludes these machines. This would'nt be my preferred approach though.