I've got a situation with a new MECM server running 5.00.9078.1000 ... Clients were not registering after install. Here is some background info:
We have two domains not in the same forest: acme.lan (legacy domain with a "." in the NETBIOS name which can't be used in Azure) and acme (technically acme.com but the ".com" isn't in the NETBIOS name allowing us to use Azure services). Due to the domain name problem, we are engaged in migrating from .lan to .com.... A legacy MECM server was in .lan and clients were pointed to it. 99.9% of computers are in the .lan .... The new MECM server is in .com
I had successfully pulled in all 400 servers. I was working on the 3,075 workstations. I was having difficulty pushing the client from the console, so I wrote a PS script (I can share this is desired) to do it remotely. I noticed that clients were fully installing, but not registering (grey question mark). I checked component status and found errors on the MP. I started digging and found IIS logs giving 500 errors and some 400 errors. In Googling, I read suggestions of uninstalling and reinstalling the MP. I tried that but now the MP will not reinstall due to a 1603 error. I have contacted Microsoft but they have not been helpful to date. I am desperate to get this resolve. I can provide any logs if needed.
We have two domains not in the same forest: acme.lan (legacy domain with a "." in the NETBIOS name which can't be used in Azure) and acme (technically acme.com but the ".com" isn't in the NETBIOS name allowing us to use Azure services). Due to the domain name problem, we are engaged in migrating from .lan to .com.... A legacy MECM server was in .lan and clients were pointed to it. 99.9% of computers are in the .lan .... The new MECM server is in .com
I had successfully pulled in all 400 servers. I was working on the 3,075 workstations. I was having difficulty pushing the client from the console, so I wrote a PS script (I can share this is desired) to do it remotely. I noticed that clients were fully installing, but not registering (grey question mark). I checked component status and found errors on the MP. I started digging and found IIS logs giving 500 errors and some 400 errors. In Googling, I read suggestions of uninstalling and reinstalling the MP. I tried that but now the MP will not reinstall due to a 1603 error. I have contacted Microsoft but they have not been helpful to date. I am desperate to get this resolve. I can provide any logs if needed.
