Replicating a deployment server across a network
I have been tasked with configuring and deploying a Microsoft Deployment Toolkit server to one of our satellite offices.
We already have a MDT server in our main office, so I would like to set up the original server to replicate changes made to it to the secondary server in our remote office. That way I don't have to spend as much time administering them.
The new server will be on a different sub-net. So it will be far easier to stand up a new server down there than try and force the system use a fixed IP for configuration or try to NAT the DHCP address that it assigns for a new machine back to our parent network.
I am looking at using Microsoft Distributed File System for this process, but I thought I might ask some people with more experience than myself if they had any suggestions
We already have a MDT server in our main office, so I would like to set up the original server to replicate changes made to it to the secondary server in our remote office. That way I don't have to spend as much time administering them.
The new server will be on a different sub-net. So it will be far easier to stand up a new server down there than try and force the system use a fixed IP for configuration or try to NAT the DHCP address that it assigns for a new machine back to our parent network.
I am looking at using Microsoft Distributed File System for this process, but I thought I might ask some people with more experience than myself if they had any suggestions
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you activate DFS at the second server the content of this directories are moved or deleted.
if you activate DFS at the "mater" the content should be stay. make a backup copy even though.
if the files at the masterserver are removed for any reason, you are able to copy them back within minutes from the backup-copy.
I use a star topology and my existing files stay there while activating DFS.
if you activate DFS at the "mater" the content should be stay. make a backup copy even though.
if the files at the masterserver are removed for any reason, you are able to copy them back within minutes from the backup-copy.
I use a star topology and my existing files stay there while activating DFS.
Why are you copying manually when there is a method given to replicate?
Try to use one method at one time.
Also is the error
"The path 'E:\DeploymentShare' exists but is not a valid deployment share and is not empty" ?
Try to use one method at one time.
Also is the error
"The path 'E:\DeploymentShare' exists but is not a valid deployment share and is not empty" ?
==============
http://social.technet.microsoft.com/Forums/en-US/48785d30-2093-4a08-b964-495a9d7c7283/mdt-share-says-the-path-edeploymentshare-exists-but-is-not-a-valid-deployment-share-and-is-not?forum=mdt
You said you wanted to create a new deployment share. We detected that the folder existed, which is fine, but it had something in it. Because we don't know what that "something" is, we assume it's bad and generate the error that you are seeing.
Either clean out the folder or specify a different path.
-Michael Niehaus
Senior Software Development Engineer
==========================
http://social.technet.microsoft.com/Forums/en-US/48785d30-2093-4a08-b964-495a9d7c7283/mdt-share-says-the-path-edeploymentshare-exists-but-is-not-a-valid-deployment-share-and-is-not?forum=mdt
You said you wanted to create a new deployment share. We detected that the folder existed, which is fine, but it had something in it. Because we don't know what that "something" is, we assume it's bad and generate the error that you are seeing.
Either clean out the folder or specify a different path.
-Michael Niehaus
Senior Software Development Engineer
==========================
ASKER
I have already copied the deployment share over to the new server. Is there any way to clear this without deleting the contents of the secondary deployment server?