Understanding 2008R2 local admin accts
Hi,
I am not a security saavy person by any stretch and have run into several situations of late where I can not log into another server using mirrored local accts - seems I am needing to specify the hostname when logging in example: if server A running an application
needs to log into server B the credential can no longer be adminacct|password it has to be serverB\adminacct. This happened after upgrading AD to 2008R2 - according to the AD admin this is out of the box and no customization.
My question is what exactly causes this behavior? and is there a particular technet paper or description of why it is?
Of course I understand the benefits of each server being a domain isolated from other servers, but for applications requiring login credentials it is a major headache.
This also affected an install of an application that uses a remote database - a domain account is a workaround but the AD admin certainly doesn't want to be using domain accounts for applications to be able to login as a domain user.
Anyway, I have been going through TechNet and just not finding what I am looking for - and not being a security guy it is making it hard to communicate in a way security folks would understand what I am trying to say.
Thanks!
September 6th, 2011 8:27pm
Hi muddharrys,
What application do you use? How does it log into another server?
Please provide more information so we can provide accurate information.
Regards,
Bruce
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2011 10:46am


