| Author |
 Topic  |
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
 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=**********
|
VT |
|
|
Rastor728
Old Timer
USA
736 Posts
Status: offline |
Posted - 10/15/2011 : 11:37:02 PM
|
| Every now and then, I have to stop and restart the Windows Deployment services to get little boot errors like this to clear. So the old "off and on again" might help you out. Also, on my system the share folder is \\IPAddres\DeploymentShare$ for the folder name, not just Deployment$. |
What would Clark Kent do to someone who stole his identity? |
 |
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/16/2011 : 4:46:55 PM
|
First I recommend using server names rather ip addresses, but that's not why it fails.
Press F8 and do a manual net use using the exact info from X:\Deploy\Scripts\Bootstrap.ini.
The most common reasons are typoes, or account expired etc.
If you can't do a new use manually, it's not MDT's fault :)
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/17/2011 : 3:43:39 PM
|
Hi there... did change the IPaddress to Name of the server. Also tried to do a F8 and used the net use command to run the bootstrap.ini, got error "The Network Name cannot be found". But both the systems are in Hyper-V & same network (10.10.2.X), made sure that domain.com is added to "Append these DNS suffixes in the DNS tab" of the Main server(from which I would like to deploy Windows 7).
Can you please help me in that... |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/17/2011 : 3:54:25 PM
|
quote:
Originally posted by Rastor728
Every now and then, I have to stop and restart the Windows Deployment services to get little boot errors like this to clear. So the old "off and on again" might help you out. Also, on my system the share folder is \\IPAddres\DeploymentShare$ for the folder name, not just Deployment$.
Is that really an issue to have a different deployment share name, the reason I ask is I am new to this....hope you can also look at my reply for another response in this blog & let me know if there is any solution. |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/17/2011 : 6:26:51 PM
|
[quote]Originally posted by arwidmark
First I recommend using server names rather ip addresses, but that's not why it fails.
Press F8 and do a manual net use using the exact info from X:\Deploy\Scripts\Bootstrap.ini.
The most common reasons are typoes, or account expired etc.
If you can't do a new use manually, it's not MDT's fault :)
/ Johan
---------------------------------------------------------------------
I also tried to disable IPv6 in Deployment Server, I got error - A connection to the deployment share (\\ServerName\DeploymentShare$) could not be made. "Cannot reach the DeployRoot. Possible Cause: Network Routing error or Network Configuration Error" & also when I did F8 & got the following error
"X:\Deploy\Scripts>Net Use bootstrap.ini" & getting error "Syatem error 67 has occured-The network name cannot be found".
Then I had to enable both IPv4 & IPv6 in the deployment server. I ping'd the deployment server that has the image, I didnt get any response for IP4, but got response for IP6. Then I restarted the windows 7 installation (after updating the deployment share)....got error "Connection to the deployment share could not be made. Connection OK. Possible invalid Credentials".... Any solutions..... |
VT |
Edited by - mywindows on 10/17/2011 6:45:55 PM |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/18/2011 : 04:34:30 AM
|
No need to, and certainly not recommended, to disable ipv6.
When you start the boot image, it will use the info in the X:\Deploy\Scripts\bootstrap.ini to connect to the server.
After booting, press F8, try to ping the server, try to do a manual net use command, using the same info (from bootstrap.ini), and you should be able to figure out why it doesn't work. At this point it's i normal SMB client/server/network troubleshooting. Has nothing to do with MDT.
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/18/2011 : 6:37:22 PM
|
quote:
Originally posted by arwidmark
No need to, and certainly not recommended, to disable ipv6.
When you start the boot image, it will use the info in the X:\Deploy\Scripts\bootstrap.ini to connect to the server.
After booting, press F8, try to ping the server, try to do a manual net use command, using the same info (from bootstrap.ini), and you should be able to figure out why it doesn't work. At this point it's i normal SMB client/server/network troubleshooting. Has nothing to do with MDT.
/ Johan
---------------------------------------------------------------------
Will there be any issue if I have PDC(10.X.25.X) & Alternate DNS (10.X.25.X) & MDT in a Test Server (10.x.2.x) in Hyper-V & also WIndows 7 (in Hyper-V).
We dont have DHCP in the PDC,so will be assigning IP manually if we add any systems. But I have added the DHCP in the Test Environment(HYPER-V that has MDT & Windows 7 (.VHD), will there be any issue due to that, please let me know. I am also looking for solutions. |
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/19/2011 : 02:20:01 AM
|
MDT does support using static ip's during deployment, but it's a nightmare and I would never, ever, recommend it. Make sure you have DHCP available for all deployments, even if you assign static ip addresses for all the machines you deploy. Meaning WinPE will use DHCP, and the machine will use DHCP, until the static ip address is applied (later in the task sequence).
What do you mean by PDC? Do you have a Windows NT 4.0 Server? Or do you mean the DC holding the PDC FSMO role?
But back to the original issue, if you can't do a "net use" from a WinPE image to a network share on your server, you have to troubleshoot that first. Before even thinking about what MDT does...
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/19/2011 : 10:08:35 AM
|
quote:
Originally posted by arwidmark
MDT does support using static ip's during deployment, but it's a nightmare and I would never, ever, recommend it. Make sure you have DHCP available for all deployments, even if you assign static ip addresses for all the machines you deploy. Meaning WinPE will use DHCP, and the machine will use DHCP, until the static ip address is applied (later in the task sequence).
What do you mean by PDC? Do you have a Windows NT 4.0 Server? Or do you mean the DC holding the PDC FSMO role?
But back to the original issue, if you can't do a "net use" from a WinPE image to a network share on your server, you have to troubleshoot that first. Before even thinking about what MDT does...
/ Johan
PDC - Primary Domain Controller & we have Server 2008 (as DC). My doubt was, does it matter if DHCP should be in the Domain Controller or it can be in the MDT server? As in our case, since we now assign IP manually to computers, will be part or main issue for Windows 7 Test system couldnt read the Deployment share in the MDT Server (from the MDT created boot image), please let me know. |
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/19/2011 : 1:45:33 PM
|
quote:
Originally posted by arwidmark
DHCP can be on any server..
/ Johan
Thanks Johan....I will try again... |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/21/2011 : 7:21:38 PM
|
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
DHCP can be on any server..
/ Johan
Thanks Johan....I will try again...
Now, I have added the WIM to the WDS & trying to boot the client (in Hyper-V) using the PXE boot. The client is waiting for the DHCP & after sometime gets error - PX-E51 NO DHCP or ProxyDHCP server to process & gives error - Boot failure. Reboot and select proper Boot device or Insert boot media in selected boot device.
I have made sure, DHCP is running, since the WDS & DHCP is in the same Hyper-V (I did select "do not listen on port 67) & also installed Legacy Network Adapter in the Hyper-V, enabled Add option 60 to DHCP & disabled previously installed default network adapter in the Hyper-V.....any clue how to PXE boot the WIM Image....Please let me know.
|
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/21/2011 : 10:38:56 PM
|
quote:
Originally posted by mywindows
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
DHCP can be on any server..
/ Johan
Thanks Johan....I will try again...
Now, I have added the WIM to the WDS & trying to boot the client (in Hyper-V) using the PXE boot. The client is waiting for the DHCP & after sometime gets error - PX-E51 NO DHCP or ProxyDHCP server to process & gives error - Boot failure. Reboot and select proper Boot device or Insert boot media in selected boot device.
I have made sure, DHCP is running, since the WDS & DHCP is in the same Hyper-V (I did select "do not listen on port 67) & also installed Legacy Network Adapter in the Hyper-V, enabled Add option 60 to DHCP & disabled previously installed default network adapter in the Hyper-V.....any clue how to PXE boot the WIM Image....Please let me know.
Later, I tried again & From the Hyper-V, I can get to the .WIM file and boots from the network after pressing the F12, but the status shows its "Starting" and can see Microsoft | Solution Accelerators & after sometime, it stops & trying to reboot from the Network asking me to press F12 again...any clue...pls let me know. |
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/23/2011 : 05:46:04 AM
|
You should not have the legacy adapter on the PXE server (vm), only on the vm's you are trying to deploy.
So you are running DHCP/PXE on a vm, and you try to deploy other vm's, right? Do you also run DNS on that box? If so you need to set the UdpPortPolicy value, or increase the port range in WDS.
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/24/2011 : 12:44:46 PM
|
quote:
Originally posted by arwidmark
You should not have the legacy adapter on the PXE server (vm), only on the vm's you are trying to deploy.
So you are running DHCP/PXE on a vm, and you try to deploy other vm's, right? Do you also run DNS on that box? If so you need to set the UdpPortPolicy value, or increase the port range in WDS.
/ Johan
Yes I am running DHCP/PXE in a Hyper-v box (IP address - 10.10.2.X) and trying to deploy other the image to anther in the same Hyper-V.
DNS is in another box (IP 10.10.7.X)....please let me know if there is any solutions? |
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/24/2011 : 1:36:36 PM
|
Looks correct to me... Can you please run wdsutil /get-server /show:all /detailed > c:\result.txt
Upload the result.txt somewhere and post the link here (do not paste the content of the file).
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/24/2011 : 3:48:20 PM
|
quote:
Originally posted by arwidmark
Looks correct to me... Can you please run wdsutil /get-server /show:all /detailed > c:\result.txt
Upload the result.txt somewhere and post the link here (do not paste the content of the file).
/ Johan
Here is the document (Output) in the link - http://tinyurl.com/43kqa88
Another thing I noticed is when I was trying to open the command prompt & ran the command you gave - I got error - "Access is denied" when I tried to run the command in the WDS server.
But I had to run as admin to get the result.txt. I have logged as admin account, inspite of that, I got "Access is denied" will that matter?
Another info - I am getting this error when try from the Work PC (connected to Domain - DHCP/PXE in a Hyper-v box (IP address - 10.10.2.X) & DNS is in another box (IP 10.10.7.X), but when I tried at home, didnt have any issue. But when I tried at workplace -I am still getting - "PXE-E51: No DHCP or ProxyDHCP offers were received" (my apologies as I didnt mention in my previous post) |
VT |
Edited by - mywindows on 10/24/2011 3:57:20 PM |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/27/2011 : 11:35:24 AM
|
quote:
Originally posted by arwidmark
Can't see anything out of the ordinary in the output, what does the eventviewer say?
/ Johan
Hi Johan, I think, I found the issue. As we dont have DHCP environment, I assigned the static IP while capturing the image to connect to the share (as the share is in the computer which assigned with the static IP) once I assigned the static IP (which is the part in the Test Server DHCP scope, then it connected. I am new in creating Deployment server & your input & watched your videos - gave me good ideas & thanks for that.
I have one more question though, do you recommend that I need follow any good practise as I am capturing image after Static IP assigment. Please let me know if you have any link or article... |
VT |
Edited by - mywindows on 10/27/2011 11:57:28 AM |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/27/2011 : 2:43:02 PM
|
Gotcha, and yes, DHCP is required for PXE :)
When capturing the image you don't need to worry about static ip addresses at all, all network configurations is blown away by sysprep anyway.
Still to help in deploy the image later, I recommend to have a DHCP available for the deployment process, even if you do assign the static ip address to the machine you deploy.
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 10/27/2011 : 3:44:54 PM
|
quote:
Originally posted by arwidmark
Gotcha, and yes, DHCP is required for PXE :)
When capturing the image you don't need to worry about static ip addresses at all, all network configurations is blown away by sysprep anyway.
Still to help in deploy the image later, I recommend to have a DHCP available for the deployment process, even if you do assign the static ip address to the machine you deploy.
/ Johan
Any good document or online link that you suggest for using static IP address(for testing purposes), but sure I have to set up a DHCP in production while deploying OS images. please let me know. |
VT |
Edited by - mywindows on 10/27/2011 4:07:10 PM |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 10/29/2011 : 3:11:58 PM
|
No, static ip addresses for the deployment solutions is just a very bad idea... Assigning static ip addresses for the machines are totally ok, but for the solution deploying them you will be in a world of pain if you static ip addresses for the actual deployment part. I don't say it can't be done, I just say it's a very bad idea.
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 11/03/2011 : 4:02:44 PM
|
quote:
Originally posted by arwidmark
No, static ip addresses for the deployment solutions is just a very bad idea... Assigning static ip addresses for the machines are totally ok, but for the solution deploying them you will be in a world of pain if you static ip addresses for the actual deployment part. I don't say it can't be done, I just say it's a very bad idea.
/ Johan
Thanks Johan for that. Another question is do you know what ports needs to be opened in firewall, if the Deployment server and client computers are different IP networks (like., 10.X.2.X and 10.X.7.X), please let me know (mostly for connecting to shares & anyother important ones you know). |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 11/07/2011 : 11:47:02 AM
|
quote:
Originally posted by mywindows
quote:
Originally posted by arwidmark
No, static ip addresses for the deployment solutions is just a very bad idea... Assigning static ip addresses for the machines are totally ok, but for the solution deploying them you will be in a world of pain if you static ip addresses for the actual deployment part. I don't say it can't be done, I just say it's a very bad idea.
/ Johan
Thanks Johan for that. Another question is do you know what ports needs to be opened in firewall, if the Deployment server and client computers are different IP networks (like., 10.X.2.X and 10.X.7.X), please let me know (mostly for connecting to shares & anyother important ones you know).
Hi Johan, is it good to have DHCP in a WDS Server or can it be a part of Router...can you pls let me know? |
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 11/07/2011 : 9:21:32 PM
|
Running DHCP on WDS is perfectly fine as long as you do the following:
Set DHCP option tag 60 in the DHCP Offer packet (WDSUTIL /set-server /DHCPoption60:yes)
Set WDS not to listen on port 67 for incoming PXE boot requests (WDSUTIL /set-server /usedhcpports:no)
Can also be done in the WDS UI.
As for firewall ports, there are quote a few that needs to be open. Here is a list:
Microsoft CIFS, port 445/TCP (Fileshare Traffic)
IKE Client, port 500/UDP (Internet Key Exchange, IKE, Protocol)
Microsoft-DS Traffic, ports 445/TCP, 445/UDP (Fileshare Traffic)
Boot Relay, port 4011/UDP (PXE Booting)
TFPT, port 69/UDP (download boot image)
RPC, 135/TCP, (Remote Actions)
RPC High Ports, 49152-65535/TCP (For Vista and later)
/ Johan |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 11/09/2011 : 5:58:40 PM
|
quote:
Originally posted by arwidmark
Running DHCP on WDS is perfectly fine as long as you do the following:
Set DHCP option tag 60 in the DHCP Offer packet (WDSUTIL /set-server /DHCPoption60:yes)
Set WDS not to listen on port 67 for incoming PXE boot requests (WDSUTIL /set-server /usedhcpports:no)
Can also be done in the WDS UI.
As for firewall ports, there are quote a few that needs to be open. Here is a list:
Microsoft CIFS, port 445/TCP (Fileshare Traffic)
IKE Client, port 500/UDP (Internet Key Exchange, IKE, Protocol)
Microsoft-DS Traffic, ports 445/TCP, 445/UDP (Fileshare Traffic)
Boot Relay, port 4011/UDP (PXE Booting)
TFPT, port 69/UDP (download boot image)
RPC, 135/TCP, (Remote Actions)
RPC High Ports, 49152-65535/TCP (For Vista and later)
/ Johan
Thanks Johan for that. Another question is, I am trying to capture a image (with few installed applications) using ImageX (for 64 bit System version 6.1.7601.21716), but I am getting error as mentioned below - can you please give me some solutions to fix it.
C:\Program Files\Windows AIK\Tools\amd64>imagex /compress maximum /flags Enterprise /capture C:\ \Cpatured\install.wim "Windows 7 Enterprise" "Windows 7 Enterprise" /check
ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7601.21716
Files/folders excluded from image capture by default:
\$windows.~bt
\$windows.~ls
\winpepge.sys
\Windows\CSC
\Recycled
\Recycler
\$Recycle.Bin\*
\System Volume Information
\pagefile.sys
\hiberfil.sys
Scanning files and directories...
[ ERROR ] C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DAT
A\master.mdf (Error = 32)
Error imaging drive [C:\]
The process cannot access the file because it is being used by another process.
|
VT |
|
|
|
arwidmark
Old Timer
Sweden
530 Posts
Status: offline |
Posted - 11/09/2011 : 9:20:12 PM
|
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 |
Regards
Johan Arwidmark
Microsoft MVP - Setup / Deployment
http://www.deploymentresearch.com
http://www.facebook.com/DeploymentResearch
Twitter: @jarwidmark |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 11/10/2011 : 5:53:44 PM
|
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. |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
Posted - 11/21/2011 : 4:02:40 PM
|
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. |
VT |
|
|
|
mywindows
Seasoned But Casual Onlooker
Canada
39 Posts
Status: offline |
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. |
VT |
|
|
|
Topic |
|
Lite Touch Deployment-Connection to the deployment
