Solved

SCCM / MDT - Simplify deployment

Posted on 2011-03-07
8
830 Views
Last Modified: 2013-11-21
We are using a number of task sequences to deploy our corporate desktop build. Currently we are creating computer associations using the MAC address of the computer being built and then place it in a collection where the task sequence are is being advertised.

Next we boot from the CD and select the particular task sequence that we want to run. Once deployed we then need to remember to ensure that the computer is removed from the collection to prevent the task sequence being displayed to the computer thereafter.

This is obviously quite a lengthy process and relies upon giving everyone access to the SCCM console. We have also found that if the computer is being reinstalled then we need to delete the machine from SCCM before the task sequence can be seen (therefore losing historical data). Is there an easier way?



Thanks
0
Comment
Question by:aideb
  • 4
  • 4
8 Comments
 
LVL 14

Accepted Solution

by:
Abduljalil Abou Alzahab earned 500 total points
ID: 35066010
Please note that task sequence should not run again automatically if you select during advertisement wizard  "never rerun advertisement program " in schedule step -> Program rerun behavior.

Please correct me if I didn't got your point: after deployment you'll have 2 records for machine name, one marked as obsolete and one not.

You need to know that When a client is flagged as obsolete it is also marked as inactive, The Delete Obsolete Client Discovery Data task deletes obsolete client records from the Configuration Manager 2007 site database. A record that is marked obsolete typically was superseded by a newer record for the same client. The newer record becomes the client's current record, and the older record becomes obsolete.

You need to go to Site Maintenance and enable the following tasks:
1- Delete Obsolete Client Discovery Data
2- Delete Inactive Client Discovery Data
0
 
LVL 2

Author Comment

by:aideb
ID: 35068109
Thanks for the information. That will solve half the issue. I will update our task sequence to ensure it doesn't run again.

Is there any way to avoid having to create a record in SCCM with the MAC address when building machines?
0
 
LVL 14

Expert Comment

by:Abduljalil Abou Alzahab
ID: 35068617
the option that you have is to enable Delete Obsolete Client Discovery Data and Delete Inactive Client Discovery Data tasks
0
Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

 
LVL 2

Author Comment

by:aideb
ID: 35068815
Sorry, I don't think you are picking me up correctly.

I want to be able to deploy the task sequence to the deploy the operating system to workstations without having to manually create a resource record in SCCM.

At the moment it needs an SCCM administrator to create the record for the deployment engineer to be able to build a machine. If there was a way to automate this but still deploy as a task sequence????

0
 
LVL 14

Expert Comment

by:Abduljalil Abou Alzahab
ID: 35068848
Ok, now I got your point, sorry for miss understanding, for this scinario you need to deploy R2 in your configMgr if not deployed then you have to enable unknow computers on PXE role and advertise your task sequenct to unknow computer collection, but note that in this case no data migration scinario.
0
 
LVL 14

Assisted Solution

by:Abduljalil Abou Alzahab
Abduljalil Abou Alzahab earned 500 total points
ID: 35068871
For your referance:

About Unknown Computer Support for Operating System Deployment
http://technet.microsoft.com/en-us/library/cc431374.aspx

How to Enable Unknown Computer Support for Operating System Deployment
http://technet.microsoft.com/en-us/library/cc161877.aspx
0
 
LVL 2

Author Comment

by:aideb
ID: 35070890
Hi,

That looks like want I want to achieve. We don't run PXE so I carried out the process for the boot disk.

When I boot I get the error 'Failed to Run Task Sequence', 'There are no task sequences available for your computer'.

We are running R2 SP2 and MDT.

I don't understand the mechanism by which the task sequence should advertise to this 'unknown' computer. Should all task sequences be automatically advertised?
0
 
LVL 2

Author Closing Comment

by:aideb
ID: 35071049
Excellent, I realised my mistake. Although we are not using PXE, the unknown computer is part of that. I realised that we do not need to enable PXE, just the unknown computer support.

The collection was created and I sent the advertisement to it!

Fantastic!

Thanks
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Case Summary: In this Article we introduce the new method to configure the default user profile using Automated profile copy with sysprep rather than the old ways such as the manual copy of a configured profile to default user profile Old meth…
After having deployed hundreds of thousands of Terminal Services seats worldwide, I still see all the time people asking me that same old question: "If TS/RDS is that reliable why are you telling me I should reboot it that often? My DC/SQL/Exchange/…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question