We've got SCCM 2007 (v4.00.6487.2000) with Man. Console 3.0 v6.1 (Build 7601: SP1) on a Hardware Server (no VM) with Win Server 2008 R2 Enterprise for almost a year.
We used SCCM to deploy program packages and OS (Win7x64). Workstations are XP SP3 (x86 and x64) and Win 7x64.
All went very well, thanks to you, anyweb , until a few days ago.
I added some in "All Systems" Collection existing workstations to the Win7 Deployment Collection, but they didn't appear in it like usual. Pressing F5 on the Collection didn't work and Update Col. Membership didn't work either. The Man.Console hung itself up. I even wasn't able to restart the Console, so i rebooted the Site and SQL Server.
Shortly after that i got calls from some users who weren't THAT amused...
Long story short:
The Deployment Task Sequence was assigned to wrong workstations (and startet automaticaly, of course). Assignment via Colection Workstation "A", "B" and "C". But the TS was Deployed to WS "D", "E" and "F". These werent even ANY collection (only in "All Systems")
I realy don't have ANY clue WTH happened there...
To prevent this, i want to protect the TS. Like a password or a Passwordpackage run first.
If i Deploy via PXE Win PE Prompt for a Password that i defined.
In Windows (RAP; Run Advert. Prog.) it just starts and wipes the system without a prompt...
How do i prevent this? Is it Possible to ask for Password or something BEFORE the TS starts?
Is it possible to deactivate the mandatory assignment, so the TS bekomes optional AND to start from PXE?
and as a last Method: is it possible to integrate a backup of a Partition on a Fileshare?
==> wie have userdata on Partition D:\. since SCCM wipes the whole HDD we need to backup the files on D:\
on the workstation "D", "E" and "F" are the Files on D:\ gone without a backup due to the autostartet TS in RAP...
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
We've got SCCM 2007 (v4.00.6487.2000) with Man. Console 3.0 v6.1 (Build 7601: SP1) on a Hardware Server (no VM) with Win Server 2008 R2 Enterprise for almost a year.
We used SCCM to deploy program packages and OS (Win7x64). Workstations are XP SP3 (x86 and x64) and Win 7x64.
All went very well, thanks to you, anyweb
, until a few days ago.
I added some in "All Systems" Collection existing workstations to the Win7 Deployment Collection, but they didn't appear in it like usual. Pressing F5 on the Collection didn't work and Update Col. Membership didn't work either. The Man.Console hung itself up. I even wasn't able to restart the Console, so i rebooted the Site and SQL Server.
Shortly after that i got calls from some users who weren't THAT amused...
Long story short:
The Deployment Task Sequence was assigned to wrong workstations (and startet automaticaly, of course). Assignment via Colection Workstation "A", "B" and "C". But the TS was Deployed to WS "D", "E" and "F". These werent even ANY collection (only in "All Systems")
I realy don't have ANY clue WTH happened there...
To prevent this, i want to protect the TS. Like a password or a Passwordpackage run first.
If i Deploy via PXE Win PE Prompt for a Password that i defined.
In Windows (RAP; Run Advert. Prog.) it just starts and wipes the system without a prompt...
How do i prevent this? Is it Possible to ask for Password or something BEFORE the TS starts?
Is it possible to deactivate the mandatory assignment, so the TS bekomes optional AND to start from PXE?
and as a last Method: is it possible to integrate a backup of a Partition on a Fileshare?
==> wie have userdata on Partition D:\. since SCCM wipes the whole HDD we need to backup the files on D:\
on the workstation "D", "E" and "F" are the Files on D:\ gone without a backup due to the autostartet TS in RAP...
Well, as you see i'm pretty F***ed
Share this post
Link to post
Share on other sites