You'll have to forgive me because I'm not an OSD guy but I'm planning a ConfigMgr upgrade and a component of that will be upgrading to MDT 2013 Update 1.
We're currently using MDT 2012 Update 1 and for some reason it's not installed on the site server so that's one thing I want to correct. I understand that I have to integrate MDT with ConfigMgr but i'm not sure how this will effect existing stuff and that's what i'm hoping i can get clarification on. Currently I see a few MDT related packages: Deployment Toolkit Files and several Deployment Toolkit Settings packages - i have no idea what these do but i believe I need to create a new temp MDT task sequence to regenerate them. So a couple things: - will these existing packages be overwritten? - Can i continue to use them with our existing task sequences or do i have to modify the TS' with the new packages? - Is it expected to have multiple Deployment Toolkit Settings packages? - Someone has decided to just dump a bunch of scripts used in our task sequences in the source for the Deployment Toolkit Files, i'm reading a best practice might be to create a separate dir in the source for this purpose? I believe there is also some process (the temp MDT task sequence?) to generate MDT specific boot images (our existing environment just has the default configMgr ones and I'm unsure why I need MDT ones? I think the final thing is how I handle my existing MDT task sequences, do i have to re-create them? Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law.
