To kick off a ZTI in ConfigMgr, we needed a way to change the boot order remotely on our Dell devices so that the onboard NIC w/PXE booted first, after the ZTI OSD, then change the boot order back so that the Hard Disk is first.
The first link below got me going, the Dell BIOS update utility has been updated and renamed from the CCTK to the Dell Command Configure. After creating 2 new Dell packages, one to force PXEboot first, and another to put it back for HDD first, we were able to do remote ZTI. This work great for those devices that have a mangled up SCCM client, for those that have a working SCCM client, we can launch the ZTI from Software Center. http://deployhappiness.com/remotely-pxe-boot-a-computer/ http://henkhoogendoorn.blogspot.com/2011/05/using-zero-touch-installation-zt i-in.html From: [email protected] [mailto:[email protected]] On Behalf Of H.T. Vermeer Sent: Thursday, August 13, 2015 10:57 AM To: '[email protected]' Subject: RE: [mssms] RE: bypass pxe password for unattended deployments Wow ! thanks ! I will try it immediately tomorrow !!! From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, August 13, 2015 5:20 PM To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments So you're just looking for a script to enable/disable the PXE password? You should be able to do that with the Set-CMDistributionPoint cmdlet in the PowerShell module. -Phil From: [email protected] [mailto:[email protected]] On Behalf Of H.T. Vermeer Sent: Thursday, August 13, 2015 10:06 AM To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments Not necessary our task sequences are running perfectly. The whole problem came because of a bug in updates but as I said this is another issue. I can do it over and over again, no students at this moment. I can do more than 100 in one night. No problem. The problem is I cannot let the helpdesk running around the campus searching for broken PC's. And September is almost there. In worst case I will set the password manually off, restart WDS and set is in the morning back. From: [email protected] [mailto:[email protected]] On Behalf Of Marcum, John Sent: donderdag 13 augustus 2015 4:50 To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments This whole idea just scares the heck outta me. L From: [email protected] [mailto:[email protected]] On Behalf Of H.T. Vermeer Sent: Thursday, August 13, 2015 9:47 AM To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments Hi Phil, If you have a mandatory TS than you do not have f12, "only" PXE password. All want is e PS script which set it off at night and then set is back. I have tried some but none will work. Our PC wake up every night at 01:00. I make a non-compliant collection (automatically) and want to design something like that. I do not know it yet but there are many ways. The scenario: Machines to be reimaged from non-compliant collection are getting reimaged and disappear from the collection. After they have run the TS there is a shutdown scheduled via GPO every early morning. Greetings, Hanna From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: donderdag 13 augustus 2015 4:16 To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments If you are setting the password on the Distribution Point properties, then Mike is correct.it will bypass the password at the beginning of the Task Sequence wizard and proceed directly into the mandatory Task Sequence. You should not need to "remove a password from the PXE" in this scenario. As also mentioned, another issue you may have to account for is the standard F12 requirement to PXE boot, but that too can be bypassed. The bigger questions are: how are you designating which machines are getting reimaged, and how are you initiating the reboot of those systems? -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ( <mailto:[email protected]> [email protected]) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 <http://www.projectleadership.net/> www.projectleadership.net <http://www.linkedin.com/in/philschwan> Description: Description: linkedin_logo-19x20 <https://twitter.com/philschwan> Description: Description: Twitter-Logo1-20x20 <http://myitforum.com/myitforumwp/author/philschwan> Description: Description: wordpress-logo3 Description: Description: Description: Description: Description: Arrow emailLead with Strategy. Leverage Technology. Deliver Results. From: [email protected] [mailto:[email protected]] On Behalf Of H.T. Vermeer Sent: Thursday, August 13, 2015 8:44 AM To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments When a password is set on the PXE server it will also apply for the required TS ! We cannot remove a password from the PXE because is used by all organization, faculties, departments etc also at the daytime. This is not an option. I am doing multicast of let us say 300 pc at once, this works. To solve the problem we have has no use because the problem is too complex and I have no time. (there is something that has caused it but it is another topic) I cannot make a package which will set the BIOS PXE boot because the packages will not run on many systems. They will stuck "in progress" or "error" What I can do is doing in manually in the evening and setting on in the morning but we want to use this kind of imaging on regular basis. From: [email protected] [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: donderdag 13 augustus 2015 3:22 To: [email protected] Subject: RE: [mssms] RE: bypass pxe password for unattended deployments Correct Mike - A required TS will bypass the PXE password. From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: 13 August 2015 14:06 To: [email protected] Subject: Re: [mssms] RE: bypass pxe password for unattended deployments If you have a mandatory deployment, the password is supposed to be bypassed. At least that has been my understanding all this time. We don't have a password on the boot image so I can't say for sure. We have a setup similar to what it sounds like your setup is. Our build is 100% PXE and never originates from within the full OS. When we do mass rebuilds we have the mandatory build deployment and a few moments prior we have a package that sets the system to PXE boot at the next boot cycle (a BIOs setting) and then triggers a reboot. The machine reboots, PXE boots, finds the mandatory build deployment and it's off to the races. Have you given it a try? Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCSE, MCTS, MCITP, MCSA, MS [ <http://www.mycertprofile.com/Profile/5319166625> Profile ] [ <http://thesystemsmonkey.wordpress.com/> Blog] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb I will rise when I have fallen. "Unless you try to do something beyond what you have already mastered, you will never grow." -Ralph Waldo Emerson From: < <mailto:[email protected]> [email protected]> on behalf of "H.T. Vermeer" < <mailto:[email protected]> [email protected]> Reply-To: " <mailto:[email protected]> [email protected]" < <mailto:[email protected]> [email protected]> Date: Thursday, August 13, 2015 at 8:47 AM To: " <mailto:[email protected]> [email protected]" < <mailto:[email protected]> [email protected]> Subject: [mssms] RE: bypass pxe password for unattended deployments Hi John, It will not work. We have a problem with running applications and TS on 1000 PC's. The log files are showing totally different pattern. Reimaging manually costs too much time. I want to reimage all of them at night. They will not run the Task Sequence from within Full OS. L Hanna From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: donderdag 13 augustus 2015 2:29 To: [email protected] Subject: [mssms] RE: bypass pxe password for unattended deployments If it's got a client already installed, you can push the task sequence to it as required. Be careful with this. I'm sure many have lost their jobs messing this up. From: [email protected] [mailto:[email protected]] On Behalf Of H.T. Vermeer Sent: Thursday, August 13, 2015 8:23 AM To: [email protected] Subject: [mssms] bypass pxe password for unattended deployments Hello ! We want to do some unattended deployments at night but we do have a password set in PXE. Is there a way to avoid the password prompt ? We do not use MDT so I suppose an own password popup as a 1 st step will not be visible for the user. Thank you in advance! Hanna ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues _____ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
