[mssms] RE: SCCM 2007 Prestaged Media with Multiple Task Sequences

2015-01-20 Thread Dave West
We did look at putting multiple images on the disk but it's not supported by 
Prestaged media as there can only be a single image referenced.

We could go down the custom scripts route but we really want to keep it as 
simple as possible.

Dave

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Andreas Hammarskjöld
Sent: 19 January 2015 14:48
To: mssms@lists.myitforum.com; mdt...@lists.myitforum.com
Subject: [mssms] RE: SCCM 2007 Prestaged Media with Multiple Task Sequences

Get all your images on one part each? Then use your sequence do decide which 
ones to keep.

Or if you don't care about the time, include media for all images on disk, and 
use sequence decide??

//A

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West
Sent: den 19 januari 2015 15:45
To: mdt...@lists.myitforum.commailto:mdt...@lists.myitforum.com; 
mssms@lists.myitforum.commailto:mssms@lists.myitforum.com
Subject: [mssms] SCCM 2007 Prestaged Media with Multiple Task Sequences

We want to build a prestaged image for our OEM using our Windows 7 64-bit 
image.  However, what will happen if another task sequence is selected that 
uses a different image, say Windows 7 32-bit, when the computer is deployed on 
site?

I ask as the documentation says that the prestaged media will have the task 
sequence variable _SMSTSMediaType = OEMmedia which means that it will skip the 
'Format and Partition Disk' step (assuming you add the check condition) and it 
will automatically skip the 'Apply Operating System Image' step.  This variable 
does not check as to what specific image has been applied, it assumes that the 
task sequence you are running references the same image used when creating the 
prestaged media image.

So, if the prestaged media image uses a 64-bit image and we select a task 
sequence that uses a 32-bit image, according to the documentation, the task 
sequence it will still skip the 'Format and Partition Disk' and either skip the 
'Apply Operating System Image' step altogether, or if there is logic built in 
to detect the image used compared to that being applied, it will apply the 
32-bit image over the top of the 64-bit prestage image already on the disk.  
Either way the deployment is wrong.

To combat this we have tried adding a signature file to our images and then 
adding a task to set a task sequence variable based on the existence of the 
signature file.  If the file matches the image used in the task sequence then 
we skip the 'Format and Partition Disk' step as documented, however if the file 
does not match (i.e. the image to be applied is not the same as the prestaged 
image) then we do perform the 'Format and Partition Disk' step.  The problem is 
that even though we have formatted the disk, because the task sequence variable 
_SMSTSMediaType = OEMmedia the 'Apply Operating System Image' step fails as it 
is looking for the prestaged image.

How can we use prestaged media images but still allow other images (task 
sequences) to be applied without having to use separate boot media?

Can anyone help with this?

Dave West
Senior Operations Analyst
Room 301 Babbage Building | Plymouth University | Drake Circus | Plymouth | PL4 
8AA | UK
Tel: 01752 587247tel://+44752587247/ | Email: 
dave.w...@plymouth.ac.ukmailto:dave.w...@plymouth.ac.uk
[cid:image001.png@01D0299F.2666E200]


[http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass

This email and any files with it are confidential and intended solely for the 
use of the recipient to whom it is addressed. If you are not the intended 
recipient then copying, distribution or other use of the information contained 
is strictly prohibited and you should not rely on it. If you have received this 
email in error please let the sender know immediately and delete it from your 
system(s). Internet emails are not necessarily secure. While we take every 
care, Plymouth University accepts no responsibility for viruses and it is your 
responsibility to scan emails and their attachments. Plymouth University does 
not accept responsibility for any changes made after it was sent. Nothing in 
this email or its attachments constitutes an order for goods or services unless 
accompanied by an official order form.



[http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass

This email and any files with it are confidential and intended solely for the 
use of the recipient to whom it is addressed. If you are not the intended 
recipient then copying, distribution or other use of the information contained 
is strictly prohibited and you should not rely on it. If you have received this 
email in error please let the sender know immediately and delete it from your 
system(s). Internet emails are not necessarily secure. While we take every 
care

[mssms] RE: SCCM 2007 Prestaged Media with Multiple Task Sequences

2015-01-19 Thread Andreas Hammarskjöld
Get all your images on one part each? Then use your sequence do decide which 
ones to keep.

Or if you don't care about the time, include media for all images on disk, and 
use sequence decide??

//A

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Dave West
Sent: den 19 januari 2015 15:45
To: mdt...@lists.myitforum.com; mssms@lists.myitforum.com
Subject: [mssms] SCCM 2007 Prestaged Media with Multiple Task Sequences

We want to build a prestaged image for our OEM using our Windows 7 64-bit 
image.  However, what will happen if another task sequence is selected that 
uses a different image, say Windows 7 32-bit, when the computer is deployed on 
site?

I ask as the documentation says that the prestaged media will have the task 
sequence variable _SMSTSMediaType = OEMmedia which means that it will skip the 
'Format and Partition Disk' step (assuming you add the check condition) and it 
will automatically skip the 'Apply Operating System Image' step.  This variable 
does not check as to what specific image has been applied, it assumes that the 
task sequence you are running references the same image used when creating the 
prestaged media image.

So, if the prestaged media image uses a 64-bit image and we select a task 
sequence that uses a 32-bit image, according to the documentation, the task 
sequence it will still skip the 'Format and Partition Disk' and either skip the 
'Apply Operating System Image' step altogether, or if there is logic built in 
to detect the image used compared to that being applied, it will apply the 
32-bit image over the top of the 64-bit prestage image already on the disk.  
Either way the deployment is wrong.

To combat this we have tried adding a signature file to our images and then 
adding a task to set a task sequence variable based on the existence of the 
signature file.  If the file matches the image used in the task sequence then 
we skip the 'Format and Partition Disk' step as documented, however if the file 
does not match (i.e. the image to be applied is not the same as the prestaged 
image) then we do perform the 'Format and Partition Disk' step.  The problem is 
that even though we have formatted the disk, because the task sequence variable 
_SMSTSMediaType = OEMmedia the 'Apply Operating System Image' step fails as it 
is looking for the prestaged image.

How can we use prestaged media images but still allow other images (task 
sequences) to be applied without having to use separate boot media?

Can anyone help with this?

Dave West
Senior Operations Analyst
Room 301 Babbage Building | Plymouth University | Drake Circus | Plymouth | PL4 
8AA | UK
Tel: 01752 587247tel://+44752587247/ | Email: 
dave.w...@plymouth.ac.ukmailto:dave.w...@plymouth.ac.uk
[cid:image001.png@01D0299F.2666E200]


[http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass

This email and any files with it are confidential and intended solely for the 
use of the recipient to whom it is addressed. If you are not the intended 
recipient then copying, distribution or other use of the information contained 
is strictly prohibited and you should not rely on it. If you have received this 
email in error please let the sender know immediately and delete it from your 
system(s). Internet emails are not necessarily secure. While we take every 
care, Plymouth University accepts no responsibility for viruses and it is your 
responsibility to scan emails and their attachments. Plymouth University does 
not accept responsibility for any changes made after it was sent. Nothing in 
this email or its attachments constitutes an order for goods or services unless 
accompanied by an official order form.