a) Use DFS share for MSIs installed from GPOs b) If you have an AD domain, then use startup/login scripts configured in GPOs, not in the user account properties of AD. The scripts are stored in the GUID folder named for each GPO, not in the NetLogon share. You can store the actual executables on a DFS share. The executables will then be replicated according to your file replication policies to your nominated file servers, not to DCs (which I think gives you more flexibility)
Cheers Ken > -----Original Message----- > From: Jim Dandy [mailto:[EMAIL PROTECTED] > Sent: Thursday, 12 June 2008 3:03 AM > To: NT System Admin Issues > Subject: RE: Executing programs from a login script > > Thanks. > > What about managed software that AD pushes out when a system boots up? > Where's the best place to put that? I've been putting it in a DFS > share. > > Curt > > > -----Original Message----- > > From: Carl Houseman [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 11, 2008 9:50 AM > > To: NT System Admin Issues > > Subject: RE: Executing programs from a login script > > > > In most cases, where there's no good reason to do otherwise, use the > > default > > locations as your standard. When another admin has to follow-up on > > your > > work, they won't have to learn the things you needlessly customized. > > > > So yes, it's the best place. And it's replicated. > > > > -----Original Message----- > > From: Jim Dandy [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 11, 2008 12:45 PM > > To: NT System Admin Issues > > Subject: RE: Executing programs from a login script > > > > Is that the best place to put logon scripts? I was just getting ready > > to set one up and I was thinking of putting it on a DFS share. > > > > > -----Original Message----- > > > From: Free, Bob [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, June 10, 2008 1:22 PM > > > To: NT System Admin Issues > > > Subject: RE: Executing programs from a login script > > > > > > The default location of NETLOGON should be something like > > > \SYSVOL\sysvol\example.com\SCRIPTS unless you changed it when you > ran > > > dcpromo > > > > > > ________________________________ > > > > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, June 10, 2008 11:48 AM > > > To: NT System Admin Issues > > > Subject: RE: Executing programs from a login script > > > > > > Miller Bonnie L. <[EMAIL PROTECTED]> wrote on 06/10/2008 > > > 02:41:00 PM: > > > > > > > I think you're thinking of the one where you copy it to the > > netlogon > > > > share. Then, you can access it using syntax like: > > > > > > > > %0\..\ifmember.exe dostuff > > > > > > The NETLOGON share! That was what I was trying to think of .... > > > > > > > I've only tried this in the old-style logon scripts (assigned on > > the > > > > user accounts). I think the %0\..\ means look in the current > path, > > > > > > But what would the current path be? The current path of the > > workstation > > > executing the login script? > > > > > > > so maybe with a newer-style script you just put it in the same > > > > location as the .bat/.cmd/.vbs file that runs it? > > > > > > I think the share name would be > > > > > > \\DC-Name\SYSVOL\DOMAIN-NAME\ > > > > > > Thanks for the reminder ... I'll poke at it a bit ... > > > > > > > > > > > > > > -Bonnie > > > > > > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > > > > > > Sent: Tuesday, June 10, 2008 10:51 AM > > > > To: NT System Admin Issues > > > > Subject: Executing programs from a login script > > > > > > > > > > > > I know I should know the answer to this, but I'm old, and it's too > > > > hot (it's 100F here in Philadelphia at the moment). Anyway, in my > > > > Win2000 AD, I want to execute a login script for a particular OU. > > > > And in this login script, I want to check group memberships and > map > > > > drive letters accordingly. Not being all that confident in > > VBscript, > > > > I was going to use the "IfMember" utility from the Resource Kit. > > > > What I'm drawing a blank on is where to copy the utility so that > it > > > > is accessible at login time. I want to call it from the SYSVOL > > > > share, don't I? Where would I copy the EXE to, what path, so that > I > > > > can execute it from the login script? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
