That's an interesting way of doing it. How long do you have to wait before you'll see the TS after booting into WinPE?
On Thu, Apr 2, 2015 at 1:20 PM, Giroux, Eric J <[email protected]> wrote: > We use a media hook script to stage the client to a re-image collection > in SCCM – so only machines booted with our media have a TS deployment > available – minimizes the risk of deploying to a bigger collection. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Chris Carbone > *Sent:* Wednesday, April 1, 2015 4:58 PM > *To:* [email protected] > *Subject:* RE: [mssms] RE: Re-imaging computers without deleting sccm > object > > > > I really don’t like the idea of advertising a TS that could re-image a > computer. I decided to just make a new OU and target my TS to that OU. So > if someone needs to reimage a computer, they need to first move computer > object into this OU. > > > Works like a charm, thanks all for your help. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Ryan > *Sent:* Wednesday, April 01, 2015 12:15 PM > *To:* [email protected] > *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm > object > > > > You can't change a deployment from available to required without doing > some very unsupported things in the database. > > Can it be done in SCCM 2007? If so, maybe a deployment to All Systems is > just what you need to get that upgrade started! > > > > On Wed, Apr 1, 2015 at 6:45 AM, ccollins9 <[email protected]> wrote: > > "Advertise the task sequence to All Systems, boot media/pxe only. > That’s how we’re doing it in the 2012 system we’re setting up now, seems to > work like a charm." > > > > I wouldn't ever recommend anyone do this unless you have reallllllly tight > control (permissions) over SCCM and ALL the techs working it know it well. > All it takes is someone setting that advertisement to "required" and then > all the computers in your domain will be re-imaged. Granted there is a > safety net there with PXE/Boot Media option, but if a computer reboots and > has PXE enabled, wouldn't it boot to PXE and begin the image installation? > > > > > > My recommendation is to give the lower level technicians access to delete > machines in certain collections. SCCM is designed to be used by everyone > from end-user to the highest tiers of support. You can lock many things > down with permissions. We package the SCCM console and push it to all our > techs in the IT department. They have the console, but can only do what > they have permissions for. > > > > Another method and maybe a safer one if the above scares you---SCCM 2012 > supports PowerShell commands. Create a service account with permissions to > delete objects using the Remove-CMDevice command and script it. > > > > > > > > On Wed, Apr 1, 2015 at 7:26 AM, Jessie Twaddle <[email protected]> > wrote: > > The unknown systems works great for unknown systems, but what do you do > when SCCM already knows about the computer and the staff who deploy the > images have no access to SCCM? Rather then have them contact Sccm admin > every time they need to reimage, I just use wds to deploy the base image. > It would be great to use SCCM always. If anyone has an automated way > around this issue, please let me know. > > Jessie > > On Apr 1, 2015 4:33 AM, "Trond Karstensen" <[email protected]> > wrote: > > I always advertise to «all systems» pxe & media only, and to all unknown > computers. > > And password protect the TS. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jeff Gilbert > *Sent:* tirsdag 31. mars 2015 22.29 > *To:* [email protected] > *Subject:* RE: [mssms] RE: Re-imaging computers without deleting sccm > object > > > > Available to all unknown systems is the ticket: > https://technet.microsoft.com/en-us/library/dn818437.aspx > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Juelich, Adam > *Sent:* Tuesday, March 31, 2015 4:23 PM > *To:* [email protected] > *Subject:* Re: [mssms] RE: Re-imaging computers without deleting sccm > object > > > > Rule of thumb is to never deploy anything to 'All Systems.' Unless you're > into extreme sports or something.... > > > *-----------------------------------------------* > > *Adam Juelich* > > Pulaski Community School District <http://www.pulaskischools.org> > > Client Management Specialist > > 920-822-6075 > > > > On Tue, Mar 31, 2015 at 3:20 PM, Rob Glodt <[email protected]> wrote: > > Advertise the task sequence to All Systems, boot media/pxe only. That’s > how we’re doing it in the 2012 system we’re setting up now, seems to work > like a charm. > > > > Rob Glodt > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Chris Carbone > *Sent:* Tuesday, March 31, 2015 1:15 PM > *To:* [email protected] > *Subject:* [mssms] Re-imaging computers without deleting sccm object > > > > We currently need to delete the computer out of SCCM each time we want to > image a computer. Is there a way where we can image a computer without > doing this? We want it to stay in SCCM for asset management from another > system that is pulling from SCCM. > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > > > ------------------------------ > > Confidentiality Notice: This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > and privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > > > > > > > > > > > > > > > > > > > > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > >
