![]() The upside is it'll reduce network traffic on other installs, as this isn't an Autodesk-only issue, Autodesk just happens to be the only ones with a weird enough install process to make Windows throw up red flags. We don't have a fix yet but I have a feeling it's going to involve firewall rules to stop DFS from acting this way. IMO this isn't a viable workaround because I'm not going to create a separate deployment for each office we have and for each Autodesk software package. Products and versions covered Issue: How to create the SCCM Software Installation Package for Autodesk software. If I "bypass" DFS by pointing the PDQ deployment directly to the local server share, it works fine. ![]() In the case of these Autodesk deployments, the initial installer at some point calls the "ProcessManager.exe" which requires admin rights, and was causing windows to freak out and flag it as "outside the network" since it was sometimes trying to open that file from an office across our WAN and not the server down the hall. This usually works, except DFS doesn't always pick the server local to the machine getting the deployment, it picks the one that responds first. We have PDQ Central server set up along with DFS so we can push deployments from one PDQ server to all of our remote offices. As a general rule, if someone has flair, they almost definitely know what they're talking about.So I think I tracked down the reason I'm having trouble with this, figured I would follow up here in case it helps anyone else.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |