Rocket Man

If it is a build and capture then you have to set up an OS installer and point it to the full source files...with an OS image setup you just need the wim file without all other files...... You say that after the TS finishes(at what stage does it finish?) it produces this error.....but does it not try and capture it after it has built the OS?

Hi set a command line component in the TS and enter in reg.exe ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v EnableLUA /t REG_DWORD /d 0 /f and set a time out of 1 min. This should be done anywhere after the setup windows and configuration manager.......and then after this simply add a restart command...the disable UAC will immediately take affect with the restart, thus not requiring the first logon user to restart it.

Is your OS installer valid?? Have you tried new installer files?

Hi Have you configured the SQL ports (TCP port 1433 and 4022) for SQL replication between sites??

Have you actually changed this registry key?? Personally I feel this is fine to do in a LAB environment but I would not change this or mess about with the likes of it in a production environment.... a simple restart of the WDS on the DP will flush the cache out if you need a hasty deployment after a failed one or a second attempt.

OK I am not sure by what you mean now........ so the 1st successful attempt was by deploying the OSD deployment to a known computer collection with your system in it?? Then Now you are trying to PXE boot this system as an unknown computer once you have deployed the TS to the unknown Computer Collection and also deleted the account from the all systems collection in the SCCM console?? If this is the sequence you have taken......then have you configured your PXE/DP for unknown computer support??

Is it that you have deleted the unknown computer objects(x86 & x64) from the unknown collection?? OR Have you just deleted a previous successful OSD system account from SCCM and are now trying to redeploy to it as unknown?

I suspected this Peter...just did not have time to test.....will now attach package to TS with query and next time deployment occurs I will know. Thanks

No....The wake up time in power management will only wake up machines if they are asleep or hibernating...it does not cold start them like WOL can do You have enabled your SCCM site for WOL. You can now deploy on a schedule if needs be OSD or software and set the WOL configuration when setting up the deployments to send a wake up packet first to the target machines to wake them up and recieve the deployments.

Out of band supports only proV NICs...so not unless your computer suites are prov enabled then not much point enabling this role. You can still use WOL though without OOB Rocket Man

I dont think it is disable DP you have to do it is REMOVE DP! Just remove the checkmarks on PXE tab on DP Check that the WDS role has removed (10-15mins maybe less depending if it is a local PXE point or remote PXE on a remote DP) Delete the Remote Install folder manually once the role has been removed from the last step. Probably best to restart the server at this stage (WDS/PXE server) What I would do at this stage is manually add the WDS role from server manager but do not configure it. Once the role has added restart the server again. Now add the PXE to the DP(this will now just have to configure the WDS for you now as you have already manually installed it from the last step). Check WDS server that it has connected and configured by opening up the console and expanding out the nodes. Check the RemoteInstall folder for extra directories and making sure the extra SCCM directories have been created and populated with files (SMSBoot x86/x64) Rocket Man

Same sometimes happens with my test lab.......probably due to overtesting....once a fresh install is done any deployment works as it should. Rocket Man

Hoping some one can point me in the right direction. I have extracted and created a driver package for a specific model. I have attached this driver package to my TS with the appropriate WMI query. This TS also services 3 other models with driver packages and WMI queries set accordingly. Once deployed the WMI query works great it only installs the appropriate driver package to the specific model. My problem is that this particular driver package does not install all the drivers for the model even though it has all the drivers needed. I found the problem and have rectified it. Basically I needed to create a single package for one of the drivers using a script. Once the script is ran it does install the missing drivers. What I need is some sort of query that will check at OSD time that this package should only install on a particular model. I do not want to have to create a seperate TS for this model and attach this extra package. Is there a way around this...maybe something similar to querying the WMI....maybe the driver WMI query does work for the package...I have not tested it, and have not got time to test either. Anyone any ideas. Thanks Rocket Man

Have you tried creating the office package again? What space is left on the client cache on the XP machines maybe it is full?? Rocket Man

Not getting what you mean...... You enter these credentials at the initial creation of the capture ISO, it should not request this input when you run it on a machine to capture it???? Is this what is happening? Rocket Man

Is the machine you are PXE booting known to SCCM? OR Is it a new out of the box machine? Rocket Man

No need to.. This is only needed where there is a hirearchy.... CAS, PS and secondary sites to allow the replication of data between DBs, thus the reason as to why it is not needed in your scenario on a single PS. Rocket Man

Is your PXE to unknown computers?? If so make sure that the machine that you are trying to PXE is not known to SCCM by checking all systems......if it is known you can simply delete the account from SCCM console and then try again. Rocket Man

Have you tried it singular via a task sequence(custom task sequence...not imaging task sequence) or just a deployed program?? Rocket Man

So i created the dos bootable usb. (do i add the dell utility to the store also after this?) I boot up and enter in ASSET_A209.exe /S xxxxxxxxxxxx and nothing happens?? Must be doing something wrong? What is the exact command I have to run.. Cheers Rocket Man

Hi Has anyone installed the ConfigMgr 2012 SP1 Beta on a Lab consisting of SQL server 2012? Has it fixed the blank reporting Instance when trying to install reporting services? OR Is this a SQL server 2012 SP1 fix? Rocket Man

Apparently it is bad idea to install and capture an OS with client on it because of it's unique identifier...but sure it is going to get overwritten with a new client at OSD time anyway at the setup configuration time!! When exactly does it bomb out on you?? Have you tried to push out an OS to this alienware machine to see if it is successful...rather than trying to capture it unsucessfully....see if it works and if not then it is a driver issue!! And also could you not install the OS on a VM with custom software if needed and capture this.....package your drivers for your alienware machine and attach to TS...same outcome you'll find as trying to capture the alienware OS...and redeploying it!! One driver has to be injected into the boot.wim in order for a connection to be made to the share at PXE enviornment time but also in some cases you need to pump in the driver into the OS via a driver package after the OS is installed at apply driver time....I had an awful time with a particular model until I actually added the NIC driver to the boot.wim and also injected it into the OS at apply driver time!! Edit: Once you injected the drivers into the boot.wim....you have created a new capture ISO and specifying to use the new updated boot.wim I gather??? If not then this could be your problem if you are using a pre-created capture ISO before you injected the driver into the boot.wim!! Rocket Man

Well if you think of it this way all your clients installed on your machines at different times more than likely...so already with a default install of the client(60 mins polling schedule), all the clients will not pole at same time.......machines may start up in the morning /afternoon and may pole at the same time, but this poling traffic is only light, it is when there is actual software to be installed that will tax the network....but this is what BITS is used for to overcome heavy network usage! Rocket Man

Also it should not matter what kind of driver(Vista) you use at PXE enviornment time...once it is able to establish the share connection...it is at the apply driver time after the OS is installed that you have to worry about what driver gets injected into the OS Rocket Man

Trust me Fujitsu is a nightmare to handle and I guarantee you it's the NIC driver that is the problem.....I use to have just WDS implemented and it has the same idea with injecting drivers into the boot.wim to get it to succesfully deploy OS.... There is a website for Fujitsu drivers...you will have to keep searching...try Fujitsu UK....I eventually found a website way back....and by all means inject both drivers into it to make sure.. Rocket Man