Comments on: New for MDT 2010: ZTIDomainJoin.wsf http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/ Sat, 28 Aug 2010 20:06:14 +0000 hourly 1 http://wordpress.com/ By: walid_zohair@rayacorp.com http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-315 walid_zohair@rayacorp.com Thu, 29 Jul 2010 21:10:45 +0000 http://tmintner.wordpress.com/?p=243#comment-315 how to edit Unattend.xml to remove the join domain ? how to edit Unattend.xml to remove the join domain ?

]]> By: MDT 2010 Deploy Windows 7 – Join the computer to the domain - Ying Li(MVP) at myITforum.com http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-290 MDT 2010 Deploy Windows 7 – Join the computer to the domain - Ying Li(MVP) at myITforum.com Sun, 13 Jun 2010 16:19:01 +0000 http://tmintner.wordpress.com/?p=243#comment-290 [...] blog talks about the workaround for scenario like this, I followed the instruction [...] [...] blog talks about the workaround for scenario like this, I followed the instruction [...]

]]> By: Ying http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-289 Ying Thu, 03 Jun 2010 16:56:07 +0000 http://tmintner.wordpress.com/?p=243#comment-289 Hi, I have a similar problem where automatic domamin breaks MDT (because we have a GPO in place to deploy SCCM Client). I am trying to use the method you mentioned above but I have some confusions regarding your instructions So I remove the domain join entries in CS.ini; add a TS (ZTIDomainjoin.wsf) to the "end" of deployment; where I put those "Variables"? Thanks, Hi,

I have a similar problem where automatic domamin breaks MDT (because we have a GPO in place to deploy SCCM Client). I am trying to use the method you mentioned above but I have some confusions regarding your instructions
So I remove the domain join entries in CS.ini;
add a TS (ZTIDomainjoin.wsf) to the “end” of deployment;
where I put those “Variables”?

Thanks,

]]> By: Joseph Ozdemir http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-269 Joseph Ozdemir Wed, 14 Apr 2010 06:25:42 +0000 http://tmintner.wordpress.com/?p=243#comment-269 Hi Keith, Just after some advice here - I want to use ztiwindowsupdate.wsf to install all approved updates from a WSUS server, however due to domain policy windows updates are disabled (We're still using SMS for workstation patching)...therefore script fails. Unfortunately my application installations are running from a dfs share on the network so I'm not sure how well authentication is going to go without the machine being on the domain prior to application installation. Is there any way you can think of that I can structure my task sequence in such a way as to 1) Pull Windows Updates from WSUS, 2) Join Domain using ztidomainjoin.wsf and 3) Install Applications. I'm aware though that there is a post application installation Windows Update task be default in the sequence, but I'd like to think that I would receive most windows updates with just the one task? Any ideas you might have would be greatly appreciated. Cheers, Joseph Hi Keith,

Just after some advice here – I want to use ztiwindowsupdate.wsf to install all approved updates from a WSUS server, however due to domain policy windows updates are disabled (We’re still using SMS for workstation patching)…therefore script fails.

Unfortunately my application installations are running from a dfs share on the network so I’m not sure how well authentication is going to go without the machine being on the domain prior to application installation.

Is there any way you can think of that I can structure my task sequence in such a way as to 1) Pull Windows Updates from WSUS, 2) Join Domain using ztidomainjoin.wsf and 3) Install Applications.

I’m aware though that there is a post application installation Windows Update task be default in the sequence, but I’d like to think that I would receive most windows updates with just the one task?

Any ideas you might have would be greatly appreciated.
Cheers,
Joseph

]]> By: Richard Tracy http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-261 Richard Tracy Wed, 07 Apr 2010 08:23:49 +0000 http://tmintner.wordpress.com/?p=243#comment-261 Can u post detailed instructions on how to deploy using the refresh/replace and unattendjoin method that have static IP assigned to the hosts? I have been successful at getting the task sequence to capture the current hosts network configurations and applying them to the litetouch PE so it can connect to the deployment share, but I can't get LitetouchPE to pass the network settings after it has deployed the OS (windows 7 ) but before it tries to join the domain. Obviously it will fail and once I manually insert the the correct network configurations, and start the litetouch.wsf sequence again it will contiune the rest of the process and finish the deployment...but now I must join the computer to the domain myself. Any ideas? Can u post detailed instructions on how to deploy using the refresh/replace and unattendjoin method that have static IP assigned to the hosts?
I have been successful at getting the task sequence to capture the current hosts network configurations and applying them to the litetouch PE so it can connect to the deployment share, but I can’t get LitetouchPE to pass the network settings after it has deployed the OS (windows 7 ) but before it tries to join the domain. Obviously it will fail and once I manually insert the the correct network configurations, and start the litetouch.wsf sequence again it will contiune the rest of the process and finish the deployment…but now I must join the computer to the domain myself. Any ideas?

]]> By: tmintner http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-224 tmintner Tue, 09 Mar 2010 16:19:05 +0000 http://tmintner.wordpress.com/?p=243#comment-224 One thing to check to see is if the machine existed in that container already before the domain join. When you are joining a machine to the domain that already exists in the domain it will always stay in the OU or container that it was originally part of. One thing to check to see is if the machine existed in that container already before the domain join. When you are joining a machine to the domain that already exists in the domain it will always stay in the OU or container that it was originally part of.

]]> By: Stephen http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-223 Stephen Tue, 09 Mar 2010 08:27:59 +0000 http://tmintner.wordpress.com/?p=243#comment-223 Hi, I've got a strange problem using SCCM and MDT 2010, the domian join always works, but sometimes the machine account ends up in the default OU instead of the one specified in the Task Sequence step. It only happens very occasionaly, and there's nothing of use in the NetSetup.log file as the actual domain join has been successful. Can anyone provide any ideas of where to look next? Thanks. Hi,
I’ve got a strange problem using SCCM and MDT 2010, the domian join always works, but sometimes the machine account ends up in the default OU instead of the one specified in the Task Sequence step. It only happens very occasionaly, and there’s nothing of use in the NetSetup.log file as the actual domain join has been successful. Can anyone provide any ideas of where to look next?
Thanks.

]]> By: keithga http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-221 keithga Fri, 05 Mar 2010 22:02:12 +0000 http://tmintner.wordpress.com/?p=243#comment-221 Eben, (Sorry about the delay in responding)... Yes, if you do nothing at the start of the MDT installation process, the machine will automatically be joined to a Workgroup. YOu can then add the ZTIDomainJoin.wsf script at the *end* of the MDT installation process, just before the final reboot, that should be good. Eben,
(Sorry about the delay in responding)…
Yes, if you do nothing at the start of the MDT installation process, the machine will automatically be joined to a Workgroup. YOu can then add the ZTIDomainJoin.wsf script at the *end* of the MDT installation process, just before the final reboot, that should be good.

]]> By: Eben http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-216 Eben Fri, 26 Feb 2010 14:58:50 +0000 http://tmintner.wordpress.com/?p=243#comment-216 keithga - Thank you so much for this help! I am new to MDT and this is my first deployment for a large company. I allso struggle for days with the GPO that renamed the local admin account. I removed the Domain Join Entries from the ZTIConfigure.xml script, and it is now not jouning the Domain at the beginning. I want to join a workgroup at that point, which is correct. What do I have to do to have to workgroup name auto filled in and continue without my interaction at that stage? Your help is much apreciated!!! keithga – Thank you so much for this help! I am new to MDT and this is my first deployment for a large company. I allso struggle for days with the GPO that renamed the local admin account. I removed the Domain Join Entries from the ZTIConfigure.xml script, and it is now not jouning the Domain at the beginning. I want to join a workgroup at that point, which is correct. What do I have to do to have to workgroup name auto filled in and continue without my interaction at that stage?

Your help is much apreciated!!!

]]> By: tmintner http://deployment.xtremeconsulting.com/2009/12/08/new-for-mdt-2010-ztidomainjoin-wsf/#comment-138 tmintner Thu, 17 Dec 2009 20:01:58 +0000 http://tmintner.wordpress.com/?p=243#comment-138 ZTIDomainJoin is pulling the variables from the wizard values that you populated when you started the deployment process or from variables in the customsettings.ini. The unattend.txt file would be used for a complete deployment if you were installing XP from source files. When you capture the image, it uses sysprep.inf. When the image is deployed the sysprep.inf in the image is used and updated with variables from the deployment. ZTIDomainJoin is pulling the variables from the wizard values that you populated when you started the deployment process or from variables in the customsettings.ini.

The unattend.txt file would be used for a complete deployment if you were installing XP from source files. When you capture the image, it uses sysprep.inf. When the image is deployed the sysprep.inf in the image is used and updated with variables from the deployment.

]]>