Solution is at hand.
When something nags at the back of your skull when doing installations that maybe a 'security setting' is wrong. Go with that. That tingle is a skill developed over years of pain and agony that comes from banging the head repeatedly into the wall.
I was working on this with a 'green' network admin and each time that I requested to have Admin rights he was making sure that I had 'local' machine admin rights.
Well they are all the same "aren't they"
After 26 hours of working on getting FRx and Integration Manager to work on 3 different computers, I can calmly state in crystal clear terms that 'green admins' will understand
NO
I sat with the 'green admin' on line this morning and went over every connnection and when I saw who he was entering for Admin - I stopped him and got to work as Domain Admin. That is when issue two cropped up.
He said, while when we mirrored these computers from their old windows 7 system they were not connected to the domain, only he created them as local admin. After which he added them to the domain still as the local admin.
When I finally got to him and explained Domain Admin is owner of ALL he realized he was working at cross purpose - his College Prof once told him that only local admins should work on workstations and only domain admins should work on Servers.
I have since set him straight on this point.
Long story short.
Connected and logged in with Domain Administrator login and forced the security to allow DomainAdmin to work correctly, we had GP, IM and FRx fully installed, patched and generating reports in 15 minutes from the start of the launch of the GP installation.
Needless to say, we are going to do a factory restore on 3 workstations, add them to the domain correctly, then do an installation as Domain Admin and be functional with a couple of hours.
CASE Closed - thanks for all the input and advise - but not much would help until we figured out the security problem.
Share
Report
22,647
All responses (
Answers (
