lorencarter
Member
- Messages
- 12
- Reaction score
- 1
- Points
- 3
I have two virtual Windows 2012R2 servers in play here. One of them is just fine and dandy in ConfigMgr 2016, release 1910.
As soon as I add this other one, the previously good cient goes inactive. They each have their own Name and IP address. But as soon as I install the client (either manualy of as a push from ConfigMgr), the original one goes bye-bye. I can get it back by deleting both devices from the ConfigMgr console, uninstalling both clients, then reinstalling the original one back.
When the client is installed on the second device, it never shows as a device, but the existing one goes inactive. At the console, the Ctrl Panel app for Configuration Manager is there, the site is correct. Everything looks like it happened. Just not at the ConfigMgr console.
I looked through my list of 300+ devices for a possible IP adddres conflict, but found none.
The "problem" server is a TEST system, so I can tinker at will. The "good" one is a Production Server. As long as I do not introduce the TEST version, it stays good. We use SCCM solely to patch and update the Windows Servers with the monthly offerings from Microsoft.
Thoughts and ideas will be appreciated. With the virus still at large, we are all working remotely,
Loren Carter
Montgomery College, Rockville, MD
As soon as I add this other one, the previously good cient goes inactive. They each have their own Name and IP address. But as soon as I install the client (either manualy of as a push from ConfigMgr), the original one goes bye-bye. I can get it back by deleting both devices from the ConfigMgr console, uninstalling both clients, then reinstalling the original one back.
When the client is installed on the second device, it never shows as a device, but the existing one goes inactive. At the console, the Ctrl Panel app for Configuration Manager is there, the site is correct. Everything looks like it happened. Just not at the ConfigMgr console.
I looked through my list of 300+ devices for a possible IP adddres conflict, but found none.
The "problem" server is a TEST system, so I can tinker at will. The "good" one is a Production Server. As long as I do not introduce the TEST version, it stays good. We use SCCM solely to patch and update the Windows Servers with the monthly offerings from Microsoft.
Thoughts and ideas will be appreciated. With the virus still at large, we are all working remotely,
Loren Carter
Montgomery College, Rockville, MD
