Easy to do with GPP or with a script.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
-Original Message-
From: Juned Shaikh [mailto:jsha...@gmail.com]
Sent: Sunday, January 15, 2012 5:16 PM
To: NT System Admin Issues
Subject: Quarterly Admin passwor
cusrmgr.exe from the Windows 2000 resource kit.
Z
Edward E. Ziots
Senior Informational Security Engineer
CISSP,Security +,Network+
> From: mich...@smithcons.com
> To: ntsysadmin@lyris.sunbelt-software.com
> Subject: RE: Quarterly Admin password change
> Date: Sun, 15 Jan 2012 22:
We're using eGuard Post which was bought by Quest I believe.
- Sean
On Jan 15, 2012, at 1:16 PM, "Juned Shaikh" wrote:
> I am trying to identify how are you folks managing the security requirement
> of changing Local admin password of all servers quarterly?
>
> Thanks in advance,
> ~ Finally
2:49 PM
To: NT System Admin Issues
Subject: RE: Quarterly Admin password change
+1, that is pretty easy one. Also make sure you rename it to something else
than "Administrator" and create a dummy admin account which is only a "Guest"
and disabled, and audit its attempted use f
ailto:ntsysadmin@lyris.sunbelt-software.com>
> Subject: RE: Quarterly Admin password change
> Date: Sun, 15 Jan 2012 22:42:35 +
>
> Easy to do with GPP or with a script.
>
> Regards,
>
> Michael B. Smith
> Consultant and Exchange MVP
> http://TheEssentialExchange.com
>
anuary 15, 2012 2:49 PM
> To: Heaton, Joseph@DFG; NT System Admin Issues
>
> Subject: RE: Quarterly Admin password change
>
>
>
> +1, that is pretty easy one. Also make sure you rename it to something else
> than "Administrator" and create a dummy admin account whic
System Admin Issues
Subject: RE: Quarterly Admin password change
+1 just did that myself via GPP. Our "local admin maintenance GPO" does two
things:
* Renames the local admin account.
* Sets the password on the added-in local administrator account.
Dave
From
To: NT System Admin Issues
Subject: RE: Quarterly Admin password change
Keep this in mind -
http://blogs.technet.com/b/grouppolicy/archive/2008/08/04/passwords-in-group-policy-preferences.aspx.
Thanks,
Brian Desmond
br...@briandesmond.com<mailto:br...@briandesmond.com>
w - 312.625.14
Subject: RE: Quarterly Admin password change
Date: Mon, 16 Jan 2012 20:07:56 +
Shouldn’t you also disable the default local Administrator account, and create
a new one, NOT named Administrator?
Joe Heaton
ITB – Windows Server Support
From: ed ziots [mailto:ezi...@hotmail.com]
Sent
y, January 16, 2012 2:43 PM
To: NT System Admin Issues
Subject: RE: Quarterly Admin password change
Saw that. My mitigation is to use the GPO for a week then nuke it, as our
standard builds show follow the new PW convention and the GPO is to just catch
up the previously-built systems.
Thoughts?
: David Lum [mailto:david@nwea.org]
Sent: Monday, January 16, 2012 2:43 PM
To: NT System Admin Issues
Subject: RE: Quarterly Admin password change
Saw that. My mitigation is to use the GPO for a week then nuke it, as
our standard builds show follow the new PW convention and the GPO is to
just catc
Alan Davies [mailto:adav...@cls-services.com]
Sent: Tuesday, January 17, 2012 1:30 AM
To: NT System Admin Issues
Subject: RE: Quarterly Admin password change
The purist would say having non-unique passwords for common accounts is a
vulnerability itself, never mind how you set them! ;o)
For thos
t;
> *Brian Desmond*
>
> *br...@briandesmond.com*
>
> * *
>
> *w – 312.625.1438 | c – 312.731.3132*
>
> * *
>
> *From:* David Lum [mailto:david@nwea.org]
> *Sent:* Monday, January 16, 2012 2:43 PM
> *To:* NT System Admin Issues
> *Subject:* RE: Qua
E. Ziots
Senior Informational Security Engineer
CISSP,Security +,Network+
From: david@nwea.org
To: ntsysadmin@lyris.sunbelt-software.com
Date: Tue, 17 Jan 2012 14:11:08 +
Subject: RE: Quarterly Admin password change
OK I’m sold.
Are you guys talking about products like this
e
>
> From: Alan Davies [mailto:adav...@cls-services.com]
> Sent: Tuesday, January 17, 2012 1:30 AM
> To: NT System Admin Issues
> Subject: RE: Quarterly Admin password change
>
> The purist would say having non-unique passwords for common accounts is a
> vulnerability itself, never
15 matches
Mail list logo
