Adam K

Hi, thanks for your replies, I've not managed to get this to work yet. I've gone into Client Agents > Software Inventory Client Agent > Inventory Collection, and added *.txt files in the location %SYSTEMDRIVE%\WINDOWS\System32\Identification\, however when I browse a given computers Resource Explorer, under Softwre > File Details, I still only see the .exe files SCCM had descovered previously. I have forced a few client machines to run the Software Inventory Cycle, which does does run, but the .txt files are not being descovered. Any idea's why? Do I have to modify to sms_def.mof file? How does this method differ over using "Desired Configuration Management" and what are its benifits?

I want to have a few collections dynamically populated based on whether they have a specific file on their machines. For example, I have a collection called 'IT staff', where every member of the IT dept will have a file saved in their C:\ root called: ITDept.txt (for example). The collection will see that this file exists and populate the desired collection with all machines that have this file. Any ideas where to begin? I can get SCCM to query for .exe files and installed programs, but can't find where to specify the files extension. Thanks

Nice one, cheers. However, it turns out that we pretty much have at least one computer with every Operating System on the list of 'specified client platforms', which is really annoying. We only have 1 machine running Windows 2000 so I've set it to run on that, seems to work fine on the other computers, they're not seeing the advert anymore, but can still PXE boot and run the task sequence. Seems a bit stupid that we have to get around the issue by doing that though.

I've got my SCCM build working nicely now, and I can deploy operating systems from PXE to both known and unknown computers, now i'm trying sort out the logistics of deploying to a few machines one at a time. Prior to SCCM, we used WDS for OSD, where you could F12 any machine and it would give you the options to re-build/image the computer. I want the same sort of thing again, i.e. I don't want to have to go into the SCCM console to manually add a computer a specific collection (i.e. "Deploy WIndows 7") that has an OSD task sequence permenantly advertised to it. Now I could have the OSD task sequence permenantly advertised to 'Unknown Computers', which would work, but only on the machines that don't have their GUID/MAC details recorded. Also I suppose I could permenantly advertise the task sequence to 'All Client Workstations', but then when the workstation is built, there will always be the OSD advertisment visible within Windows. I suppose I could surpress the advertisment messages, but it still seems a bit sketchy. Is this the only way to achieve what I'm after?

Thanks for your comments guys, unfortunately before I was unable to resolve the error the hard drive array on my piece of crap server failed and now i've lost everything and have to start again with a new server! Just for hell of it, I tried a manual install of Windows 7 on a VM using the Windows 7 ISO media that I had extracted for OSD, strangely the installation kept prompting for a storage driver which I could never match. I downloaded the ISO image again, for a 3rd time, tried the manual install on the same VM and it didn't ask for a driver at all and completed installation successfully, so my guess is the problem could have possibly been related to a dodgy Windows 7 image?? I'm not convinced though, because I was initially using the same extracted OS that worked perfectly in my first attempt of setting up SCCM. Looks like its back to starting from scratch...AGAIN! 3rd time lucky ay ;-)

Nope, I left the product key entry option empty, the deployed clients will automatically be activated by our KMS server (if they ever deploy) Anyone know if the installation will complete if I don't add any drivers to the Boot Image(s)? I'm using machines that contain fairly common generic drivers and Windows usually installs them automatically. Or are the Boot image drivers absolutely required? I know that I have been able to PXE boot and run the first task sequence without adding any drivers to the boot image previously. But again, it fails at the same point. I really just want to rule out Drivers as the issue if possible.

I have had an absolute nightmare with this, since I posted my last message I tried removing the PXE service point, uninstalling WDS, adding it all in again but then I started getting these errors preventing PXE from downloading the boot image: "PXE-T01: File not found" and "PXE-E3B: TFTP Error – File Not Found"! I've just resolved that by following this guide. I was kinda hoping that stripping it down to the extent I did and fixing it again would magically make the OSD task sequence work, but it turns out I'm back to the same stage I was at earlier! I've attached the SMSTSLog file, but I can't see anything obviously wrong on it, maybe you guys will spot something. smsts.log

Nah I'm not using Native mode, i'm in Mixed mode. Smsts.log is saved on the client right? The machines I'm working on have no OS, how can I extract the log file from the client? My Task Sequence is as follows: 1. Format and Parition Disk: Disk number = 0, Disk type = standard(MBR), Volume (Partition Type = Primary), (99% of remaining free space), (File system=NTFS, quick format) 2. Apply Operating System Image: Apply operating system from an original installation source (OS package selected) 3. Auto Apply Drivers 4. Apply Windows Settings: company name, workgroup etc. 5. Apply Network Settings: But its not getting past step 2 so would that not suggest it cannot be related to the Setup Windows and Config Manager step?

Hi guys, this problem is driving me mad, and I've wasted 3 days on trying to resolve it so far to no avail. Basically when I try to deploy Windows 7 via PXE boot, the Task Sequence always fails when trying to install the OS, and throws the error message "Task Sequence sequence name has failed with the error code (0x80004005)...". I've read threads that suggest this error code relates to certificates, and in the smspxe.log the only errors appearing are as follows: WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode. smspxe 11/07/2011 12:30:19 2488 (0x09B8) WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. smspxe 11/07/2011 12:30:19 2488 (0x09B8) WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. smspxe 11/07/2011 12:30:19 2488 (0x09B8) WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. smspxe 11/07/2011 12:30:19 2488 (0x09B8) But surely these aren't relevant as i'm not using certificates?? This is actually the second time I've built SCCM up on this server and I'm using the same settings and config as before (which worked). I can PXE boot, and select the advertisment I want to run, it then proceedes to format and partition the hard drive successfully, but then failes as soon as it begins the task of installing the OS. I have tried removing all drivers from Boot images, re-adding them in (only the network adapters), rebooting the sever, deleted the Windows 7 OS Install Package and re-creating it (even re-downloaded the image), I've re-created the advertisments, removed the PXE boot images from the distribution points and added them in again, nothing has fixed it!! I've read this problem is sometimes related to drivers, but I'm using the same drivers as I did in the previous installation. Should the PXE OSD work even if I didn't add any drivers to the Boot Images? I tried and it got to the same point as it is going now. Please help!

OK, so after some messing about with WebDav and setting the DNS suffix on the advanced TCP/IP of the SCCM server's NIC, I am now able to deploy the client to any machine in my collections. This includes the creation of teh CCM and ccmsetup folders in 'system32' directory (whereas before it would only create the 'ccmsetup' directory. Also now it creates all the icons in Control Panel: 'Configuration Manager', 'Remote Control' and 'Run Advertised Programs'. HOWEVER, within the SCCM console it still shows Client = No; Assigned = Yes, for the machines that do have it installed. Also when I try to deploy applications the workstations nothing happens, so something is still a miss. The server side ccm.log is still complaining about the following: CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e ---> Unable to connect to WMI ® on remote machine "DT5047", error = 0x8004100e And workstations are still complaining about: <![LOG[Failed to successfully complete HTTP request. Please, any other suggestions?

The client push account is a domain administrator account which has all the rights required to install software on local machines. I have even logged the machines on as the same account to ensure its not the local accounts that are restricting the installation. Windows firewall is disabled on all machines, so that can't be blocking it. I'm at a bit of a loss here

I know this is a fairly common issue, however i've read mutliple threads to no avail, so I figured last hope is to post my own thread. I've recently built up this SCCM 2007 server (fully updated, services packs and all) - installation went without a hitch, SQL is installed on a seperate machine but all permissions were apparently fine. I cannot get software to deploy to my workstations (or the SCCM client to install on workstations remotely). My descovered computer 'Collections' are fully populated, with all machines showing: Site Code = LBR, Assigned = YES, Client = No. Even though I have manually forced instalations of the client on a couple of machines, they are still showing no client on the SCCM console. I have tried to deploy Office 2007 to these machines to see if it works anyway, but it doesn't. Admin account specified to install applications is correct, and of course I have been Updating Collection refreshing My workstations do seem to have the sccm client installation initiated, but I keep seeing this message on the logs of my workstations: <![LOG[Failed to successfully complete HTTP request....etc. and <![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="12:31:37.870+-60" date="04-01-2011" component="FSPStateMessage" context="" type="3" thread="1608" file="fsputillib.cpp:1253"> On the SCCM server, SMS trace is also showing the folling for the ccm.log: 'Unable to connect to WMI ® on remote machine "LT5068", error = 0x8004100e' I have attached snips of logs from the Workstations (ccmsetup.log) and from the SCCM server (Server - ccm.log) if anyone wishes to have a look. Thanks ccmsetup.log Server - ccm.log