Thank you to all that has responded. If anyone else has anything to add or if some uses a method that has not been discussed, please feel free to add to the discussion.
Lots of good information and food for thought. BR, Dave L. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Wilson, J Kevin Sent: Tuesday, November 15, 2016 1:17 PM To: mdtosd@lists.myitforum.com Subject: [MDT-OSD] RE: Best methods to replicate MDT content I have used DFS-R for replication of WDS boot images. Used one-way replication, and replication only pushes the differential. DFS-R also makes the equivalent of a "combined" WIM (e.g. multi-WIM) for you - single instance storage - data is unified in one .RWM file. It offers MS supported replication and lots of consoles and logs to monitor things. Not sure about options for unique downstream files. Kevin Wilson From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of ODONNELL Aaron M Sent: Monday, November 14, 2016 4:27 PM To: 'mdtosd@lists.myitforum.com' <mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>> Subject: [MDT-OSD] RE: Best methods to replicate MDT content *** Exercise caution. This is an EXTERNAL email. DO NOT open attachments or click links from unknown senders or unexpected email. *** 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: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry Sent: Monday, November 14, 2016 1:00 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> 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
