MattW

Very true - I stand corrected

When you say software do you mean a package or an application? Only Applications are visible in the software catalog - you need to create the application, distribute it, then deploy it (not deployment type) and it will show up. There's a good little guide here : http://wibier.me/?p=104 *edit* just noticed you mentioned errors in those components - what do they say? Cheers, Matt

Hi, Just a quick (and unhelpful) update - I gave up on this in the end and reinstalled the lab from scratch (everything on a single VM this time) and OSD works flawlessly now so I can only attribute this to some sort of installation mishap or user incompetance Cheers, Matt

Hi Sam, The client that SCCM will be trying to deploy is by default here : C:\Program Files\Microsoft Configuration Manager\Client - depending on where you installed it to ofc. That has both the 32 and 64 bit client but you just need to invoke ccmsetup.exe on your target machine to install the SCCM client. (although it sounds like you`ve found it - no need to modify permissions there - SCCM handles that) Regarding the components, I wouldnt worry about WSUS for the moment - that will have no impact on client deployment and to be honest I always get a boat load of errors after a new SCCM install on that - until the WSUS role has done an initial sync and SCCM has got it's database sorted out I tend to just ignore the status of it. The important one to have a look at is the MP Control Manager - if your management point is having difficulties it could explain why the client isnt behaving. Finally, have you configured an account for client push? Go to the Administration tab, Sites, then right click your site and select Client Push Installation and have a look around there. It could be you arent allowing installations to workstations, or maybe you just need to set an account with admin rights on the target computer. Cheers, Matt

Hi, Obvious questions I guess but have you configured your site boundaries to use your AD site(s)? If so, have you tried setting them as subnet boundaries instead? Have you configured a network access account that sccm can fall back on to install the client? Finally what happens on the client OS when you try to install it? Do you get any SCCM folders / logs? Cheers, Matt

Hi Peter - definitely messed with certs. I installed SCCM in mixed mode and have configured as much as I can to use HTTP but I noticed that it seemed to require a root CA certificate so as a long shot I installed an enterprise root CA, exported the cert and imported it into SCCM. The only other certificate related work I did was installing the root CA cert and the OSD self signed cert into Trusted Root Certificate Authorities store on the SCCM server. More of a blind stab in the dark rather than a calculated move but either way it hasnt made much difference! matt

Hi Peter, The WDS/PXE is on one server (the SCCM one) and DHCP is on a different server (SQL) which is why I configured them - from what I understand you shouldnt really have to do that but I`ve found that it doesnt work properly if you dont (things like No Boot File etc). **edit** also this isnt about PXE as such due to the same error cropping up when using TS Media - more to do with SCCM not recognising the computer - some sort of uber unknown device Cheers, Matt

Hi folks, Been trying out the new version of SCCM and run into a bit of a brick wall. I have SCCM2012 installed on one VM (2008 R2, which is also the mini-lab DC) and a seperate VM running SQL 2008. I`ve installed the WDS role (both bits) and enabled PXE on the DP, made both boot images available for PXE and distributed them to the DP (and the DP Group for good measure). Next, I installed the DHCP role on the SQL box, added option 66 & 67 so it knows where to go (pointing at boot\x86\wdsnbp.com (tried smsboot too)), added my Win7 image and knocked up a basic deploy task sequence. Now when I make a 3rd VM (all this is in VMware Workstation btw) and try to network boot it fails when trying to contact SCCM then goes into pxeboot.com and eventually dies. In the SMSPXE.log file I see the following : <![LOG[reply from server is 'NoReply']LOG]!><time="17:45:32.414-60" date="05-04-2011" component="SMSPXE" context="" type="3" thread="4228" file="libsmsmessaging.cpp:2108"> <![LOG[PXE::DB_LookupDevice failed; 0x80004005]LOG]!><time="17:45:32.414-60" date="05-04-2011" component="SMSPXE" context="" type="3" thread="4228" file="database.cpp:187"> <![LOG[PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="17:45:32.420-60" date="05-04-2011" component="SMSPXE" context="" type="3" thread="4228" file="pxehandler.cpp:1364"> After several hours messing about with PXE, installing certificates and poking into every nook and cranny of SCCM I then remembered I was being an idiot, and could just use the TS Media ISO to test this. So I created one of those, pointed it at my MP and fired up the 3rd VM again. That didnt go so well either, and the SMSTS.log file shows this : <![LOG[Requesting client identity]LOG]!><time="17:14:20.171+480" date="05-04-2011" component="TSMBootstrap" context="" type="1" thread="1112" file="libsmsmessaging.cpp:5700"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: DC2008SCCM2012.BETA.HOME.LOCAL:80 CCM_POST /ccm_system/request]LOG]!><time="17:14:20.171+480" date="05-04-2011" component="TSMBootstrap" context="" type="1" thread="1112" file="libsmsmessaging.cpp:8720"> <![LOG[Request was succesful - 200]LOG]!><time="17:14:20.187+480" date="05-04-2011" component="TSMBootstrap" context="" type="0" thread="1112" file="libsmsmessaging.cpp:9046"> <![LOG[reply from server is 'NoReply']LOG]!><time="17:14:20.187+480" date="05-04-2011" component="TSMBootstrap" context="" type="3" thread="1112" file="libsmsmessaging.cpp:2108"> <![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_retail\sms\framework\osdmessaging\libsmsmessaging.cpp,5798)]LOG]!><time="17:14:20.187+480" date="05-04-2011" component="TSMBootstrap" context="" type="0" thread="1112" file="libsmsmessaging.cpp:5798"> <![LOG[Failed to get client identity (80004005)]LOG]!><time="17:14:20.187+480" date="05-04-2011" component="TSMBootstrap" context="" type="3" thread="1112" file="libsmsmessaging.cpp:6047"> Again there's that "NoReply" message. Now the TS i made is advertised deployed to a collection I made where I imported the computer MAC address. I even imported the GUID and no joy. I then tried deploying the TS to the Unknown Computers collection but I`m getting nowhere. I`ve come to the conclusion that SCCM just doesnt know about the target computer hence the messages even though I`ve imported it a few times (and tried a different VM to get a different MAC just in case). Oh and I made sure my boundaries included the subnet not just the AD Site just in case that made some difference to it (it didnt). I`m guessing its something to do with the Management Point somewhere along the line, but I`ve made sure that has its Root CA cert imported (Certificate Services role as Enterprise Root CA on the DC) and there are no errors in the log so I`m kinda stumped. I could just rebuild the whole thing from scratch but I wondered if anyone here had any bright idea's before I have to do that as it's either a "feature" i`ve bumped into, or i`m doing something wrong somewhere and rebuilding it will just waste another day and I get the same problem again Only thing I cant test at the moment if this is as a result of doing it in VMware - I have a fully working 2007 lab on the same VMware install which does PXE boot a VM and build it, but maybe 2012 is not quite as happy with this... All suggestions welcomed! Matt