glen8

Hi all, We currently have a Hyper-V server running FCS 2010 and an SCCM 2007 R2 server on a VM platform. Everything working great but the boss wants to remove the Hyper-V server and run everything on SCCM. I heard that with R2 you can integrate FCS with it so you can manage your clients. I've searched through google but can't really find anything. Does anyone know if this can be done, and if so where do I find the white papers/guides. Thanks very much!!

Run this from a command prompt on your clients: WMIC CSProduct Get Name That will give you its model name. Then put the model name in the following query: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%MODEL GOES HERE%" Put that in the options tab on each of your driver pack tasks

Yes of course, I will reply tomorrow when I'm next in work. Basically you run a simple command on your client machines in DOS which reports back a text string. Earlier I did it on an HP 4000 Desktop which came back 'HP Compaq 4000 PRO SFF' and a Dell D531 Laptop which came back with 'Dell Latitude D531' When you have all the model strings for the various machines on your network you create an OSD Task and add in all the driver packs one by one (assuming you know how to do this, if not shout). Then on each driver task you click the second tab on the top which lets you set a filter. You start by selecting an IF statement and select all when the window pops up. Then you add a WMI filter. In the box you paste in a command and enter your model string. Basically when the OSD task runs it goes to the first driver package, looks at the IF statement and decides if it matches or not. If not it goes to the next driver pack and so on. I'll reply tomorrow with the commands. I've already tested it and it works a treat.

It's ok, managed to figure out how to do it via WMI filtering on the driver pack task. Didn't know you could query the WMI on a machine to get the model number. How cool!

Hi all, We currently have say 5 different models of laptops in our organisation. To simplify things I have created 5 driver folders and installed all of the drivers from the manufacturers website. Then I assigned each one to their own driver pack. so...5 driver folders and 5 driver packs. Ideally I'd like to create a single deployment task to install one wim for all 5 models of laptop. Not sure I fully understand this, but my thinking is that the Auto Apply Driver task within the OSD looks at the entire driver share and takes only what it needs. This 'should' be enough to work on all our 5 models of laptops. The problem is that it doesn't work. Currently we have 5 tasks where each one specifies it's own driver pack. Have I misunderstood how it works? Thanks

ok thanks very much, think I have got my head around it now. Guess it won't be so bad as deploying the updates from a search doesn't seem to take too long. Just one last question if you will... is there any merit in adding the following at the end of my OSD task, would this help in any way to the updates? Software Update Restart Software Update My thinking is that usually when performing manual updates you usually have to reboot it a couple of times to get them all Thanks

Thanks Peter, Would it be possible to perhaps (in some way) advertise say a rule which means any new updates automatically get advertised?

Hi all, I have created a build and capture task which I'd like to run every two months (or so) so the engineers have a fairly current build they can use when deploying new machines. Just wondering what's the best/easiest way to use the software update task within the OSD tasks. We have a single SCCM 2007 R2 site server running WSUS3.0. This has downloaded all the updates from Microsoft for Windows XP, Office 2007 and Forefront Client. The local WSUS folder which is sitting on the D:\ is 6gb. Reading a few guides it all looks very static to me as in you can't simply tell the OSD task to apply all the updates from XP RTM > Todays latest update. To me it looks like you have to create a share, then run a search folder to view all the updates via product, highlight and deploy to your share and then set that to your collection via a DP. That's all well and good today but what about in two months time when there's new updates released? Will I have to do it all again to include the new updates? The whole procedure seems very long winded to me so I'm wondering if there's a better way. It's also a waste of HDD as now I have... WSUS > SMSWSUS$ > SMSPKGD$\XXX0032 Not to mention SCCM doesn't really work with a standalone WSUS server somewhere else within the domain so that's another WSUS content folder we have LOL Thanks!

Grr, turns out the office 2007 package was corrupt. Tried installing it from the desktop and that wouldn't work either. Removed and re deployed the package and everythings working greating. The forefront client it would seem needs to be deployed once the machine is part of a domain rather than a workgroup. Thanks

mmmmm, seems things aren't quite going as planned. Most of my software installation tasks are now ok apart from the Microsoft ones (go figure). Adobe, Java, Putty, CDBurner etc etc are all ok but whenever I try and deploy either Forefront client or Office 2007 if fails with the above code 0x80070002

Unfortunately the logs are not available as it's too far along in the process. The part getting the error looked to me to be within windows xp itself rather than PE. This would explain why F8 did not bring up the DOS window. Unfortunately it's a pain that the local logs get deleted once the task sequence has completed and windows is installed. Unless they are in another location? (wouldn't surprise me being microsoft) However, I have managed to work out what the problem was. I'll post the answer here like I always do in case anyone has a similar issue. Last week we migrated the server from tier 2 to tier 1 on our SAN (to give us better disk i/o) and I believe we had some data corruption. What was happening is that the boot.wim was ok booting the machine up and deploying all the tasks but once windows had installed it didn't have any NIC drivers. Looking at the driver pack half of the drivers were missing!!!! very strange as they were all there a few days before the migration. Basically this is what was happening PXE Boot > boot.wim > integrated PE drivers within the boot.wim for NIC card Running the tasks: format c:, windows/network settings, driver pack, windows install, reboot Windows XP setup (blue screen setup, reboot, gui setup, reboot) Windows XP boots and goes back into the SCCM screen for the software install tasks. It was at this point windows was missing the NIC drivers and coming up with the 0x800... error. This explains why changing the tasks from software install to anything else also resulted in the same error. Finally I removed the driver folder and driver pack and reimported the drivers for the machine in question. Updated the DPs and relinked the pack back into the task sequence. Why microsoft can't put a simple 'Unable to access network share...' message instead of a code beats me :-)

oh yes, it's way way after that part. It goes through all the tasks formatting the HDD, applying windows/network settings, installing drivers and then windows. Windows is fully installed but it's the task straight after that which always comes up with the error.

Looks like I may be mistaken on the software part, when I remove the software installation tasks and change to a simple reboot I get the same error.

It seems no matter what software package I try to include within an OSD task, I keep getting the 0x80070002 error. Tried office 2007 SP2 using the guide on here, then tried deploying adobe reader with the help from appdeploy.com. My tasks are fine up until it gets to the software installation task, it looks like it's working as it takes 5 minutes before the 0x80070002 error. The software is on the DPs ok. The machine reboots and goes into windows xp as normal (obviously without any software installed). Does anyone know what logs I can look at? Thanks! Glen.

Hi all, SCCM 2007 SP2 on W2K8R2. Installed WSUS 3.0 on SCCM and configured it to pull updates from the web. In products I have only selected Windows XP and Office 2007/2010. I've looked in the logs and it seems to be syncing everything. My D:\WSUS now contains 40GB of data :edit: I've put the wrong thread title so please ignore Thanks!

Hi all, We have enabled AD system discovery and have 1,600 machines in the All Systems group. Great start :-) The issue I'm having is that in this group there's a split between workstations and laptops. Luckily the comapany has a good naming convention and all the workstations start with WSTN- and the laptops start with LPTP-. I've created a group with a query 'System name like WSTN-%' hoping to have a group only containing workstations. The problem is that this group only has 55 machines in it. The All System group has hundreds of machines starting with WSTN-. Weird, as I'd either expect it not to work at all or contain the 400 hundred or so workstations. Just having 55 is a bit strange any ideas? Thanks!!

Hurrah!! Downloaded an older intel driver (proset64 v16.0) which works fine. I can now boot into WinPE and do an IPCONFIG. after fixing other issues such as corrupt packages after a VM crash and for some reason having to select in the advertisement 'run from a network DP if the task can't run locally' or something to that effect it's now working :-) Thanks to everyones help, especially Chris!

oh heck!! it's just dawned on me.... if i've been adding in drivers to the boot images and updating the wrong share no wonder it's not working oh well, that's two days of my life wasted LOL

PXE Service Point? take that as a no lol I'm actually sat here at home going through a full server 2008 VMware build so I can get a SCCM lab setup. Might help me out a bit. :edit: quick google tells me the PXE service point is a role? if that's so then yes the server does indeed have a PXE role as PXE works fine on all the other boot images apart from my new one :edit: ahhhhh, think I added my boot image to the wrong location, I added it to the general DP share where all the software packages go http://technet.microsoft.com/en-us/library/bb932177.aspx Thanks again Chris, I owe you one. Just downloaded the latest win7 driver from intel again. There's ndis5, ndis61 and ndis62. Not sure if I have to add them all in or should I pick a paticular one. Damn, why is everything so complicated :-)

Thanks I'll have a look tomorrow when I'm next in work. Would you mind please telling me the location of that log? also, as a side issue yesterday I attempted to add a new boot image so I could test various drivers without messing up the boot images already installed (this is a live production server you see). I must have done something wrong because here's what I did.... configmgr console Copied boot.wim from C:\SMS_LIN\...\...\..\x64\boot.wim to C:\TEST\x64\boot.wim Clicked on Boot Images Clicked on Add new Boot Image Located my test boot.wim, next, next, finish Managed and updated the DP. Checked in the servers DP share and it is sitting in there ok. Went into my task and pointed to the newly created boot image. I cleared all PXE annoucememnts and any advertisements. Restarted WDS service just to make sure everything was good. Imported my .csv file with my machines MAC address (bare metal desktop) and assigned it my a collection. Advertised my task to the collection. Booted up the desktop and it won't PXE boot. Checked the PXE logs on the server and it has a message 'PXE no boot device found' If I set my task back to one of the original boot images already on the server it all works fine any ideas? Ideally I'd like to get a new boot image so I can test all these drivers out. Thanks, Glen.

Thanks Chris, I have been doing everything from the configmgr console. When I go into the properties of the boot image I see only the NIC drivers I want from the HP website.

Thanks for the help guys, I really appreciate it. Like I said, I'm very new at this and have taken over from the contractor so I was never involved in the installation. The server is on Windows Server 2008 R2 and it's SCCM 2007 SP2 (no R2 or R3). This afternoon I had a look at the boot images and I think the contractor got them from the C:\SMS_LIN\ folder so I assume these boot images came from SCCM itself? I've removed all the drivers from the boot image and only then installed one NIC at a time. Then I updated the DP and made sure the TS was using the correct boot wim. The driver I tried earlier was a Windows 7 driver from the HP website but it still didn't work. I doubt anything is wrong with my TS as if WinPE can't get an IP address then it won't get as far as reading the tasks. Looking at the part where it says 'Windows is loading files' the correct boot.wim is being used. I did notice an extra folder appear on the TS lists called MDT so looks like someone has installed MDT? (no idea what version though) No idea where I am going wrong :-(

Hi all, Started a new job a month ago and have been working with a contractor on SCCM 2007. Never used it before then but I am picking it up quite quickly. The contractor has gone now but we still have an ongoing issue with a new model of HP desktop. It's a HP PRO 4000 SFF and looks to have an Intel 82567V-4 NIC installed. Last week we had to deploy seven systems that day so I ended up manually building the system from CDs, then I created a USB boot disk to run SCCM to capture the image locally. Then I copied the .wim to the network. That all worked great but the issue we have is now deploying the .wim via the network on PXE boot. The other machines PXE boot into Windows PE but do not get an IP address. I have the console enabled in the boot image so can F8 into DOS. When I run an ipconfig all I get is: Windows IP Configuration Now looking on the internet it seems the boot image does not have the correct driver. I have downloaded the driver from HPs website, intels website and as a last resort toshibas website (older version) and injecting one by one the drivers into the boot image. Unfortunately none of them seem to be working ARGH! The image we are deploying is Windows XP 32bit. Just as a test I have even tried booting a Windows Vista and 7 32bit and 64bit images with the Vista/7 drivers. Even that didn't work. The boot image only has one driver at a time as to avoid any potential driver conflicts. To make matters worse we have 50 coming today we need to be built from this .wim image Please help!!!!!! Thanks, Glen.