Constraining Group Policy

  • Thread starter Thread starter jonhop85
  • Start date Start date
J

jonhop85

I'm currently trying to rollout outlook 2003 to all of the machines in
my company. In this process I'm using an .mst file that is
automatically creating the user profile and setting them up to use
exchange. Along side this process I'm attempting to release an active
directory based signature file to each user. I have a third party
script that is able to accomplish this on the command line but I'm not
able to succeed in doing this using group policy and I really don't
want to have to run the script on the command line for each user.

The problem is that the user profile doesn't get created until the user

actually opens up the Outlook for the first time, at this point the
profile is created and setup to use exchange to receive mail. Once
this has taken place the command line script for the signature file
works without a problem. The issue that I'm facing is that with group
policy the command line script is being ran prior to the profile
creation, and this causes the script to fail.


The solution I'm looking for is in regards to constraining the group
policy object from running until the profile is created. Is there a
way to make the OU dependent upon a particular file existing on a user
profile (the .pst file in this case)? Any help would be extremely
appreciated.


Thanks!
 
Group Policy is only going to filter by security group or WMI - so to do what
you're wanting you'll need to change your signature script to look for the
pst file. If it's not there then the script should fail and exit. You may
want to try one of the scripting groups for help creating the actual script.

If it's not already - the script will need to be run as a User GP (not
system) otherwise it won't know the profile to check.
 
Back
Top