| T O P I C R E V I E W |
| mywindows |
Posted - 10/15/2011 : 9:33:50 PM
Hi there....I doing a Windows 7 deployment. I have couple of systems 1. Deployement Server (server 2008 r2) in the Hyper-V. I have got the image imported and updated the deployment share & copied the image to the host server (on Server 2008 R2). Gave the "BuildAccount" modify permission & made sure the permission didnt change. When I boot the Windows7 Test System (with in Hyper-V), I am getting error "Connection to the deployment share could not be made. Connection OK. Possible invalid Credentials", Can you please let me know if there is any solutions.
My Bootstrap file is mentione below -
[Settings]
Priority=Default
[Default]
DeployRoot=\\IP Address\Deployment$
SkipBDDWelcome=YES
UserDomain=DomainName
UserID=BuildAccount
UserPassword=********** |
| 30 L A T E S T R E P L I E S (Newest First) |
| arwidmark |
Posted - 06/18/2012 : 02:29:03 AM
If you need to change that script it means something is broken in your reference image. I would rather fix the real issue than doing unsupported hacks.
The most common reason for sysprep breaking is antivirus software in the reference image...
/ Johan |
| mywindows |
Posted - 06/15/2012 : 12:44:21 AM
Hi Johan....I had the same issue as in the link mentioned below and I followed Frank's post and commented in LTISysprep.wsf like this....and also disabled the "Add mass storage drivers to sysprep.inf for XP and 2003" as well...
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/553bec59-d795-4b89-8328-19a38161eff3?prof=required
Error - ZTI ERROR - Non-zero return code by litetouch, rc = -2147467259 0x80004005
FAILURE (Err): -2147024894 0x800700002: Test for CloneTag in registry to verify Sysprep
completed. - Unable to open registry key "HKEY_LOCAL_MACHINE\System\Setup\CloneTag" for
reading.
'//oShell.RegDelete "HKEY_LOCAL_MACHINE\System\Setup\CloneTag"
'//aCloneTag = empty
'//On Error Resume Next
'//aCloneTag = oShell.RegRead("HKEY_LOCAL_MACHINE\System\Setup\CloneTag")
'//TestAndFail not IsEmpty(aCloneTag),6191, "Test for CloneTag in registry to verify Sysprep completed."
'//oLogging.CreateEntry "Contents of CloneTag(0): " & aCloneTag(0), LogTypeInfo
'//On Error Goto 0
I got the image, I will be testing the image...but also would like to know that if there will be any issues in that image...please let me know...
Can you please give me your input...Hoping to see your mail. |
| mywindows |
Posted - 02/16/2012 : 5:52:34 PM
quote:
Originally posted by arwidmark
Ah, gotcha.... What installation properties are you using on the SCCM client? Are you pushing the client, or is it failing when deployed via the task sequence?
/ Johan
Hey Johan...my apologies as I couldnt message you yesterday. I am installing client from the SCCM console --> Computer Mgmt --> Collections --> System # --> Install Client. But We came to know its the fireall issue & opened proper ports & its installing the SCCM clients on the new subnet. If I have any other SCCM 2007 questions, I will check with you. Thanks for the reply Johan...REgarding MDT if I have any question, I will check with you as well. |
| arwidmark |
Posted - 02/15/2012 : 05:46:29 AM
Ah, gotcha.... What installation properties are you using on the SCCM client? Are you pushing the client, or is it failing when deployed via the task sequence?
/ Johan |
| mywindows |
Posted - 02/14/2012 : 3:40:29 PM
Hi Johan...my apologies as I didnt mention it clearly. Its regarding the SCCM 2007 R3 clients not installing in the Client PC's in the different subnets....I can install them in the same subnet, its not installing to the client PC's in the different subnets. Hope you can help in that... |
| arwidmark |
Posted - 02/14/2012 : 3:13:18 PM
I'm sorry but I haven't done any FEP 2010 deployments (only Endpoint Protection in CM2012)...
/ Johan |
| mywindows |
Posted - 02/14/2012 : 2:39:30 PM
Hi Johan...I also setting up SCCM 2007 R3 for FEP. Can you pls give me some help in this post in this link http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/0f448a52-f235-4218-aad2-3b603aff479d
I tried to install the SCCM client and FEP 2010 in the same subnet network & it worked fine. But I am testing in a computer in different subnet (as mentioned in the post)...didnt install both the SCCM client and FEP. can you advice please.... |
| mywindows |
Posted - 02/07/2012 : 5:13:29 PM
Hi Johan...I have just mailed you those log files to your gmail from my hotmail. Please let me know... |
| mywindows |
Posted - 02/07/2012 : 12:58:23 PM
Thanks Johan, will mail you...today soon |
| arwidmark |
Posted - 02/07/2012 : 10:33:21 AM
You should see the OSDComputerName value being set, if not zip together your cs.ini and all logfiles, and mail then to me... my email alias is my lastname and I'm using gmail
If you want MDT to automatically generate names for you you can use a stored procedure in the MDT database
Generate Computernames in MDT 2010 based on prefix and a sequencenumber
http://www.deployvista.com/Default.aspx?tabid=78&EntryID=120
You can also check Part 19 - Extending the MDT 2010 Database in the MDt 2010 Unleashed video series
http://www.deploymentresearch.com/Videos/MDT2010LiteTouchUnleashedVideos.aspx
/ Johan |
| mywindows |
Posted - 02/06/2012 : 4:42:28 PM
Thanks for your Reply Johan. I checked the log & pasted the info below (but I am sure I marked the OSDComputerName in the database as different system number.
<![LOG[Property HostName is now = STC0033064]LOG]!><time="20:03:25.000+000" date="01-30-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property HostName is now = MININT-86QLLOR]LOG]!><time="20:06:00.000+000" date="01-30-2012" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
Both are from the same log file in a system. Does the above log mean that the host name is STC0033064 @ time="20:03:25.000+000" date="01-30-2012 has changed to MININT-86QLLOR @ time="20:06:00.000+000" date="01-30-2012". But right now the system number is STC0033064 (which is also different than the one that I have set. couldnt understand the above mentioned log)
Another question is that, if I set different computer names in CS.ini, do I have to mentioned as
Comp001
Comp002
Comp003 and so on or is there a format I can follow, can you help me in that pls. |
| arwidmark |
Posted - 02/06/2012 : 3:09:27 PM
Sure you can deploy 5 - 10 machines at the same time, and it doesn't require a database to set the computername to the serialnumber (if the computer have one).
Just set below directly in cs.ini. And check the ZTIGather.log to see what value it actually is using.
OSDComputerName=PC-%SerialNumber%
/ Johan |
| mywindows |
Posted - 02/06/2012 : 09:28:27 AM
Hi Johan...I would like to check if there is a way we can deploy images to multiple computers (5-10) at a time...I also was trying the DB option to input the computer name (in OSDComputerName=PC-%SerialNumber%), for some reason, it didnt get that value...Can you please advice me in that. And another question is, will you recommend MDT 2012 beta 2 in production.... |
| mywindows |
Posted - 01/06/2012 : 08:57:55 AM
Thanks Johan, will try that... |
| arwidmark |
Posted - 01/05/2012 : 6:53:38 PM
You can deploy FEP 2010 as a standalone installation with MDT 2010, and for example manage it via Group Policy.
Here is a good article on managing FEP 2010 with Group Policy
http://blogs.technet.com/b/clientsecurity/archive/2010/11/10/advanced-policy-management-with-forefront-endpoint-protection-2010.aspx
/ Johan |
| mywindows |
Posted - 01/04/2012 : 09:56:00 AM
Hi Johan...is there a way we can integrate Forefront End Point 2010 in the MDT 2010 or anyother suggestions, as we are planning on security implementation. Please let me know.
---------------------------------------------------------------------
My apologies...as I didnt mention clearly in the post...I checked the FEP 2010 implementation requirements - SCCM 2007 is required. But is there anyway we can FEP 2010 in MDT 2010 environment. Please let me know. |
| mywindows |
Posted - 12/29/2011 : 09:10:27 AM
Hi Johan, Thanks for that...Sysprep & Capture in MDT 2010 worked fine when I was testing yesterday. |
| arwidmark |
Posted - 12/28/2011 : 01:10:44 AM
You need to run sysprep before capturing the image.
Use MDT to also create the image, with or without manual actions in it. MDT will take care of sysprep and capture for you.
/ Johan |
| mywindows |
Posted - 12/23/2011 : 1:30:29 PM
Hi Johan, My scenario is - I would like to get an image of windows 7 with pre-installed application. I used ImageX for capture that computer's image (which has Test1 computer's name on it).
I was trying to retrieve computer name (for Test2 computer) , domain (Test2 computer to be joined) from the database, but I can see computer name, admin user name / password / domain / time zone settings / keyboard settings after the BDD welcome screen. Test2 computer is not joining the Domain, but I can see Test2 computer is getting installed with Test1 computer name.
Also I tried the MDT 2012, I can see the progress goes upto 49 out of 85, then computer restarts and wanted me to login locally with local admin account....not sure where I am making mistake. Any Suggestions please..... |
| mywindows |
Posted - 12/14/2011 : 2:55:13 PM
Thanks Johan, I will try that and ask if there is any questions. |
| arwidmark |
Posted - 12/10/2011 : 5:16:00 PM
For IP address use DHCP, for computer names you have a number of options available... For example to set the computer name to PC-SerialNumber you can use
OSDComputerName=PC-%SerialNumber%
You can also use the database (more advanced) to have MDT generate a computername based on prefix and a sequence number so the first pc will be PC00001, then PC00002 etc...
/ Johan |
| mywindows |
Posted - 12/09/2011 : 11:16:02 PM
Thanks for the info Johan....till now in test environment it worked fine.
I would like to ask my you...my main goal is to get a custom image from a computer & install that to multiple computers in production environment. While installing, I would like to automate (may be by using answer file) the deployment so that it allocates different IP address and different computer names in a domain using one image.
Can you give me any suggestions please. Hoping to see your message. |
| arwidmark |
Posted - 12/09/2011 : 6:44:51 PM
Yes...
Leftover junk prevents new installation in MDT 2010
http://www.deploymentresearch.com/Blog/tabid/62/EntryId/32/Leftover-junk-prevents-new-installation-in-MDT-2010.aspx
Btw, it's being fixed in MDT 2012
/ Johan |
| mywindows |
Posted - 12/09/2011 : 2:34:38 PM
Hi JOhan, thanks for your response.....Just thought of keeping you updated. Cleaned previous files (C:\MININT folder or C:\_SMSTaskSequence folder) & worked fine.
Just a question.....is there a way I automate to delete those files, just in case for future reference... |
| arwidmark |
Posted - 12/07/2011 : 7:11:07 PM
Well, either the share name is wrong on the server, or insufficient permissions, or wrong user, or still wrong in bootstrap.ini
When you start the deployment and get the error, do the following:
1. Press F8 to get a command prompt
2. Type in: "type X:\Deploy\Scripts\Bootstrap.ini" and review the content
3. Try to a net use to the server share using the info from bootstrap.ini... If you can't do a net use, troubleshoot this a normal network issue, will have nothing to do with MDT
Example: Net use \\Server_Name\DepShare$ /u:DOMAIN\UserName Password
/ Johan |
| mywindows |
Posted - 12/07/2011 : 7:04:49 PM
quote:
Originally posted by arwidmark
You need to update bootstrap.ini with the new servername and sharename, then update the deployment share, and then replace the boot image in your WDS
/ Johan
Thanks for your reply...I made sure that its pointing to the correct share name from the server DeployRoot=\\Server_Name\DepShare1$
Please let me know if there is any solutions |
| arwidmark |
Posted - 12/07/2011 : 6:59:11 PM
You need to update bootstrap.ini with the new servername and sharename, then update the deployment share, and then replace the boot image in your WDS
/ Johan |
| mywindows |
Posted - 12/07/2011 : 4:58:16 PM
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
You MUST perform the imagex capture from WinPE, it cannot be done from the running windows, and yes you need to sysprep the machine first.
Best is to have MDT do the build and capture (including running sysprep and creating the wim) of the virtual machine you use (or should be using) for reference image. A good tip is to take a snapshot before running the sysprep process in the event you want to revert and do some changes later.
/ Johan
Thanks Johan, I will try that & give you feedback.
Hey Johan, build and capture worked fine in Test environment. Looking for some adv. configuration.
Hi Johan, I am trying to capture Custom windows 7 image from a physical machine, so I can use that image in the MDT 2010 do the regular steps for deployment. (Previously, I captured the image in the Virtual environment).
Do you have any suggestions to capture the system image (which is not running) - any steps or tools you can suggest. Please let me know.
Hi Johan, I got the image & worked fine. I was trying to do the same steps again, I am getting an issue (couple of times I have noticed) - Steps I did was -
1. deleted the share
2. Deleted the folder with files as well (which I was using before as I was using the trial version of the windows 7)
3. Re-created the share with different name & Imported OS & did create the task sequence and updated the Deployment Share.
4. When I tried to install the OS using the MDT, I can see the "Microsoft Solution Accelerators" screen & its pointing to old sharename that I have deleted - getting error "A connection to the deployment share (\\Computername\Old Share Name$) could not be made. Connection OK. Possible:invalid credentials. Any clue, please let me know.
I think, I found the issue - from this link (as I tried in new computer & it worked fine) the link below -
http://social.technet.microsoft.com/Forums/zh/mdt/thread/42bccec1-e527-4d48-bfc7-2f8dee56951d
Do you know any idea the location it will write in the registry?? Please let me know. |
| mywindows |
Posted - 12/07/2011 : 11:51:17 AM
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
You MUST perform the imagex capture from WinPE, it cannot be done from the running windows, and yes you need to sysprep the machine first.
Best is to have MDT do the build and capture (including running sysprep and creating the wim) of the virtual machine you use (or should be using) for reference image. A good tip is to take a snapshot before running the sysprep process in the event you want to revert and do some changes later.
/ Johan
Thanks Johan, I will try that & give you feedback.
Hey Johan, build and capture worked fine in Test environment. Looking for some adv. configuration.
Hi Johan, I am trying to capture Custom windows 7 image from a physical machine, so I can use that image in the MDT 2010 do the regular steps for deployment. (Previously, I captured the image in the Virtual environment).
Do you have any suggestions to capture the system image (which is not running) - any steps or tools you can suggest. Please let me know.
Hi Johan, I got the image & worked fine. I was trying to do the same steps again, I am getting an issue (couple of times I have noticed) - Steps I did was -
1. deleted the share
2. Deleted the folder with files as well (which I was using before as I was using the trial version of the windows 7)
3. Re-created the share with different name & Imported OS & did create the task sequence and updated the Deployment Share.
4. When I tried to install the OS using the MDT, I can see the "Microsoft Solution Accelerators" screen & its pointing to old sharename that I have deleted - getting error "A connection to the deployment share (\\Computername\Old Share Name$) could not be made. Connection OK. Possible:invalid credentials. Any clue, please let me know. |
| mywindows |
Posted - 12/02/2011 : 3:04:48 PM
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
You MUST perform the imagex capture from WinPE, it cannot be done from the running windows, and yes you need to sysprep the machine first.
Best is to have MDT do the build and capture (including running sysprep and creating the wim) of the virtual machine you use (or should be using) for reference image. A good tip is to take a snapshot before running the sysprep process in the event you want to revert and do some changes later.
/ Johan
Thanks Johan, I will try that & give you feedback.
Hey Johan, build and capture worked fine in Test environment. Looking for some adv. configuration.
Hi Johan, I am trying to capture Custom windows 7 image from a physical machine, so I can use that image in the MDT 2010 do the regular steps for deployment. (Previously, I captured the image in the Virtual environment).
Do you have any suggestions to capture the system image (which is not running) - any steps or tools you can suggest. Please let me know. |
