Scott

This'll do me! Cheers!

Hi, I've had a request to allow F12 PXE boot to occur from any subnet (currently limited to 3 subnets). I've asked our networks team to add the IP address for the SCCM Server with PXE Role, as a helper address for all subnets. They have responded asking if it is possible for the role to migrated to one of the existing DHCP servers. The question is, is this something that any of you have done before or is it advisable? My concern is that the DHCP server would be hammered each time we deploy an OS? Wherever possible i would still like to utilize our existing SCCM servers. Hopefully this makes sense?? Cheers! Scott

After our machines have been built using SCCM OSD, I want to ensure that all of the cycles have been triggered, to ensure that all the outstanding updates and any software packages advertised to the client get installed as soon as possible. I've found this - http://www.intrntpirate.com/?p=179 However, it doesnt work for me and wondered if others had a script that worked already!? Cheers Scott

This is now resolved! I believe the issue is that when SCCM installs the Mass Storage driver, it creates around 150 folders in the C:\Drivers folder, it then reference this in HKLM>Software>Microsoft>Windows>Current Version > DevicePath. However, there is a character limit to this and therefore it wont reference the folders that contain the required inf files. My workaround for this has been to create a seperate software package with the correct drivers, a reg fix and a batch file to reinstall the drivers later in the task sequence. For anyone having this issue, the batch file contains the following: xcopy "%~dp0\3DG\*.*" "C:\HP6555b\3DG\" /Y /V /R xcopy "%~dp0\3DG\amd64\*.*" "C:\HP6555b\3DG\amd64\" /Y /V /R xcopy "%~dp0\3DG\x86\*.*" "C:\HP6555b\3DG\x86\" /Y /V /R xcopy "%~dp0\AUD\*.*" "C:\HP6555b\AUD\" /Y /V /R xcopy "%~dp0\GFX\*.*" "C:\HP6555b\GFX\" /Y /V /R xcopy "%~dp0\GFX\B_99351\*.*" "C:\HP6555b\GFX\B_99351\" /Y /V /R xcopy "%~dp0\VID\*.*" "C:\HP6555b\VID\" /Y /V /R xcopy "%~dp0\NIC\*.*" "C:\HP6555b\NIC\" /Y /V /R regedit.exe /s "%~dp0\devicepath.reg" START /WAIT RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers The xcopy lines are copying the inf files from the sourcefiles folder to the C: drive path The regedit line imports the registry with the new DevicePath %SystemRoot%\inf;%SystemDrive%\HP6555b\3DG;%SystemDrive%\HP6555b\3DG\amd64;%SystemDrive%\HP6555b\Aud;%SystemDrive%\HP6555b\GFX;%SystemDrive%\HP6555b\GFX\B_99351;%SystemDrive%\HP6555b\VID;%SystemDrive%\HP6555b\NIC And the RunDLL line updates the drivers, searching through the folders specified in the paths above. Cheers and hope this helps anyone else! Scott

Is this because of the hardware, or is it worth trialling older/newer/oem versions of the drivers? They will install using the inf, but not if i automatically search, I have to point to the inf file and install it that way. Is it possible to identify the correct path, like we used to using the sysprep driver path? Cheers Scott

Hi We have a single TS which will image both Intel and AMD devices, however the only AMD device that we have to test on, the drivers are not installing correctly. They are being copied to the C drive of the device, but are not installed, even by applying a driver package or automatically apply drivers. Currently, the workaround is to install the software that was downloaded with the software, but this also installs the rubbish software with it! (ATI Graphics and HD Audio) Has anyone ever had this? How did you get around it? Cheers! Scott

Have a look for some of the right click Tools, we have a set that will enable you to trigger any of the client actions for all of the machines in a collection. I think it was one of the sets from MYITforum,

We have decided to deploy updates through SCCM in packages by product. The idea is that we have Office 2007 all in one package, advertised against a dynamic collection with all devices with Office 2007 - the theory being that if someone is upgraded to Office 2010, they'll move collections and get all outstanding updates for Office 2010. The issue that i need clarification on is how i go about amending the packages/deployment management/whatever is required to add any new updates to it and ensure these are deployed to the devices. I'm aware that the deployment packages should be over 500 updates (?) and as far as i can see, this won't be a limitation in our environment. Cheers Scott

I've created the WinPE image using http://www.myitforum.com/absolutenm/templates/Articles.aspx?articleid=15495&zoneid=87 and this is now working. I've advertised the task sequence to all unknown computers, which seems to let you press F12 from most devices! Cheers

Cheers, i Can do this bit... Im after a couple things really: 1. Enable F12 boot for Bare Metal machines, without having to import the computer configuration into SCCM. 2. Enable F12 boot for all other machines, but without the user having the option to run it from Windows.

Hi, I want to be able to press F12 on any machine, and then be able to choose an Task Sequence, how do i go about doing this? THe thinking is that for bare metal, rather than having to import the computer data into SCCM, have a HTA Script which registers it in the PXE stage - should be possible as long as i can get it to boot to PXE! Cheers Scott

Yeh, i think so... I'll have a look into the possibilities and see which one fits us. If i do schedule the deployment at say 9pm, but the PC is switched off, does it install the following morning, or will it try daily at 9 until its on at that time?

So it should install the maintenance window before the deadline? Or would it install it the window after the deadline? In our test lab without any windows set up, it would reboot the machine (despite the reboots being supressed) if it was past the deadline? I think scheduling the updates through the client should be OK, as that is the most similar way that WSUS is currently deploying the updates. I take it that if the updates are assigned as soon as possible, the client begins the download whenever they pick it up, but doesnt install until the schedule? The main thing we want to avoid is everyone trying to download it all in one go (despite WSUS being in that situation already!)

Not yet.. But surely even if the maintenance windows were set, the updates wouldnt be installed until the deadline passes and then the tick box would allow the pc to reboot outside of the windows?

But if i set that, then the reboots will be enforced straight away and that will cause disruption? I'm considering scheduling the updates to install daily at 10, using this VBScript? dim updatesDeployment ' Create the COM object. set updatesDeployment = CreateObject ("UDA.CCMUpdatesDeployment") ' Set the local schedule by using the SetUserDefinedSchedule method ' and the recurrence and hour values passed in. updatesDeployment.SetUserDefinedSchedule 8, 10 ' Output success message. I left this message out as well. 'wscript.echo "Set Local Software Update Schedule."

Ive had a look at that and the setting was already set. I can deploy updates to devices silently, if i tick the box on the client to install on a schedule - however there doesnt seem to be a way to set this centrally? I was hoping that the updates would work in the same was as software distribution, ie, deploy as soon as possible would begin installing the next time the client sync'd? As it seems, when you set it to as soon as possible it won't install until the deadline?

Hi, We are currently looking at using SCCM to deploy windows updates, however i am having a problem with the updates getting to the clients. I would like to be able to deploy updates through SCCM, but supress any notifications and reboots - basically so that the end user can continue to work uninterupted. The update packages are set to deploy as soon as possible and the deadline is set 2 weeks in advance, however depsite synchronising the client etc the updates aren't installing. I know i should enable the notifications in testing so i can see whether anything is happening, but i would like to know whether the desired setup is even possible? To clarify, I want to pick,download and deploy updates as soon as possible, without notifications to the clients, with supressed reboots. I don't particularily want to wait until the deadline passes, as this will mean that it will reboot the machine on the deadline without warning. Is this possible? How would i go about doing it? Hopefully this makes sense? Cheers Scott

Sorry just realised i put this in the wrong forum

Hi, We are going to be using SCCM to deploy images to our devices, however currently we use sysprep to run a command file to mute the device. At what point can we do this using SCCM? Really it can only be done at first log on...? Cheers Scott

This is the driver we are using for our DC7800s, http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=ir-66362-1&prodTypeId=12454&prodSeriesId=316720 Good Luck!

I had this error for a few NIC drivers, i ended up downloading a later and older version of the drivers and they successfully imported into the package... not really a fix but it got things working.

When you advertised your OSD task did you make it available to the PXE Boot media?

THis has now been successfull after following the using the SCCM Task sequence media for capturing an image.

Yeh I am, it's also in the sysprep.inf about joining to the domain. THe thing i had forgotten to do, is manually sysprep the image before capturing the WIM, so i will try that today and update this post. Thanks Scott

Hi, I'm looking to create a sequence which installs Microsoft Windows XP SP3, Office 2003 (7), Adober Reader 9 and a few other local apps. I have created a base WIM file for just Windows, and added a task for installing each subsequent piece of software however this proves to be a slow way of doing it. SO, I created a new build with this software already installed and captured it using IMageX. I have the WIM file and can deploy this to a device, however i want it to automatically join it back to the domain with the old computer name. This is where the issue starts... The WIM image is name WIMCapture and not joined to a domain (as was good practice when creating a ghost image) so now when i run the task sequence it calls any machine WIMCapture and doesnt join it to the domain, despite the task sequence and SYSPREP telling it to do this otherwise. Can anyone shed any light on the best way for this to be done? I want a base image, which I can deploy the OS and basic apps in which joins back to the domain, with no end user input. Cheers Scott