bbrehart

Once you manually changed the Zone Transfer settings back to the way they should be, did IPAM ever change them back? And yes, it would be nice to have the option.

The saga continues: so I realized that the code signing template from the issuing CA was set to issue certs with the username in the subject line, rather than the server. I created a duplicate template for code signing and re-issued the certificate with the server name in it. Now, when I attempt to deploy the Software…

No, no progress at all. And the reason I mentioned that the processes had completed previously is that they were working at one time. I attempted to stop the tasks this morning and there was no change.

Lawrence, I've created an enterprise, code-signing cert, installed it on WSUS and deleted the old self-signed certificate. When I attempt to distribute the certificate via Patch Manager, it still shows the self-signed cert. Any ideas?

We're using a one-way trust between the domains and the DNS in the domain where the Orion server is located isn't configured with a FLZ for the other domain. The HOSTS file (in this case) was the only way to go. Thanks for all your help.

That did not work.

I had not and I'll try it and let you know what happens.

What's very strange is that most of these processes are ones that had been completed previously.

The target is a 500-node Domain and the state of the task is Running

It's true that it will discover them, but not using WMI. Any way to get this functionality?

Worked like a charm. Thanks again!

So what's the purpose of Discovery? Do we even need it?

The reason for the 3rd party is due to the fact that we're patching over two domains and one won't trust the self-signed. Also, we have our own certificate server, so we don't pay for any non-self-signed certs. I have created the certificate, so how do I import it into Patch Manager? Sorry for the confusion.

So I figured it out - the main issue was that I needed to not only set the preferred DC, but also make sure the local firewall allowed the traffic out and set the HOSTS file to point to the DC in the domain that didn't contain the Orion server.