Remember, MDT at the end of the day is just a shared folder. Nothing more; there are no services, processes, or anything else. The workbench mainly just edits a handful of XML files. So, installing WSUS on the same system has no possibility of causing any issues.
As for using the same WSUS instance ConfigMgr, I would say in a lab environment, sure no big deal. In a prod environment, I could easily see it causing updates to accidentally get deployed (among other potential ramifications) and would never it do it (it is also completely unsupported to do so). J ________________________________ From: [email protected] <[email protected]> on behalf of elsalvoz <[email protected]> Sent: Friday, February 21, 2014 12:03 PM To: [email protected] Subject: Re: [MDT-OSD] MDT and WSUS on same server In my lab I even use the instance of WSUS that SCCM uses. All 3 in the VM. It may be an unsupported scenario (no docs on it) but works, no errors on any of the applications. I point the MDT builds to get patches that I make available through WSUS directly. SCCM uses the engine to make patches available after the system is a client. On Feb 21, 2014 9:08 AM, "Brent Hutchison" <[email protected]<mailto:[email protected]>> wrote: All, I am finally getting traction in my company to get a separate server or two for reference image builds. The only question I have been asked is why should the WSUS server be on its own server. Why can't it be MDT and WSUS be on one server? I cannot seem to find a definitive answer to this question. Can they reside on the same server and be ok? I understand beefing up the specs if we do the all in one, but will it cause any other issues having them on the same server? The WSUS server will only be used for reference image builds as we are currently using ConfigMgr for all other workstaion and server updates. Thank you all, Brent
