I’ve done it with one-way DFS replication as far back as MDT 2.0 or 2003 or 
whatever the heck it was back then. Works great.

From: [email protected] [mailto:[email protected]] On 
Behalf Of George Salmaniw
Sent: Tuesday, November 15, 2016 9:34 AM
To: [email protected]
Subject: Re: [MDT-OSD] RE: Best methods to replicate MDT content

[External Email]
I use debian linux as a deployment share and rsync.
Works beautifully!

George

On Mon, Nov 14, 2016 at 4:26 PM, ODONNELL Aaron M 
<[email protected]<mailto:[email protected]>> 
wrote:
DFS sounds like it would probably be the best solution for something that 
scale.. We have a primary MDT distribution point and 5 remote Linked Deployment 
Shares, and I recently started using powershell with scheduled tasks to 
automate things. The downside is there’s no log to see if something failed but 
that hasn’t been an issue (yet).

Here is the powershell script I use to start a linked deployment share copy to 
one of those sites. I just copied it from the output from the “View script” 
button in the status window after manually updating a linked deployment share. 
The “DS905” is based on part of our server naming convention. I think it starts 
at DS001 if you just use MDT’s powershell output verbatim, but I changed it so 
each powershell script (I have one script per configured linked deployment 
share) would have a unique DS identifier so the multiple scripts could run at 
once.

Import-Module "C:\Program Files\Microsoft Deployment 
Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
New-PSDrive -Name "DS905" -PSProvider MDTProvider -Root "D:\MDT Deployment 
Shares\Production"
Update-MDTLinkedDS -path "DS905:\Linked Deployment Shares\LINKED005" –Verbose





Thanks,

Aaron O’Donnell

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of David Landry
Sent: Monday, November 14, 2016 1:00 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] Best methods to replicate MDT content

Hi All,

I need to automate replication across 3 different regional MDT servers located 
in three different regions of the world and then down to 47+/- local MDT 
servers at various sites scattered among the three regions. The flow of data 
needs to be one way, all downstream. Nothing can go upstream. Nor do I want to 
delete files on downstream MDT servers that may be specific to that particular 
site.

I am partial to DFS but am getting substantial pushback from a manager in 
another department in IT.

Before I set up a test environment to prove DFS is the best method, I am 
curious as to what everyone else uses with their pros and cons. Replicating 
through Linked Deployment shares is not cutting it at this point …. I need to 
automate it.

Thanks in advance.

Best Regards,

Dave






________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.

Reply via email to