can a GPO do this for me?

  • Thread starter Thread starter djc
  • Start date Start date
D

djc

My network has a database front end file (just an MS Access .mdb file) that
is updated almost weekly. I have used several techniques to distribute this
file to all machines on the network with varying levels of success. I'm
interested in finding out how Active Directory GPO's can do it. Below are
several questions concerning this... some I think I know but confirmation
can't hurt. I'm just looking for some initial info here to help me decide if
I should persue this.

1) can a gpo create a folder on the client's local file system? and what if
that folder already exists?

2) The main operation I'm looking for the gpo to perform is just a file
copy. I have no .msi file. Can I do this? and what if the file already
exists on the client?

3) would I be able to set the gpo up in a way that I can set it up once and
leave it? In other words, the .mdb file I need to keep up to date on the
clients can change as often as once a week (filename remains the same of
course). Can I simply create a gpo once that points to the location of the
file to copy so that all I need to do is copy over (overwrite) that file
with the new one and do nothing else?

any info is appreciated. Thanks.
 
Principle: In theory a GPO applied to machine or user
can do anything -- anything that can be done through the
registry or by running a program.

Reality: There may not be a pre-existing item to
accomplish the task/outcome and you have to decide
how hard you wish to work.

djc said:
My network has a database front end file (just an MS Access .mdb file) that
is updated almost weekly. I have used several techniques to distribute this
file to all machines on the network with varying levels of success. I'm
interested in finding out how Active Directory GPO's can do it. Below are
several questions concerning this... some I think I know but confirmation
can't hurt. I'm just looking for some initial info here to help me decide if
I should persue this.
Click to expand...

General methods to attack this problem (with a GPO):

1) Batch file that just copies the update, creating any
directories or running any programs necessary for the
installation.

2) A formal Software installation package based on an MSI
(or MSP) file.
1) can a gpo create a folder on the client's local file system? and what if
that folder already exists?
Click to expand...

Sure. A script file can do this and GPOs can run scripts, e.g.:

cd \somepath\DB
md mydatabasesubdirectory


Well, most methods would leave the directory there if it
already existed but...

cd \somepath\DB
rd /s /q mydatabasesubdirectory
md mydatabasesubdirectory
2) The main operation I'm looking for the gpo to perform is just a file
copy. I have no .msi file. Can I do this? and what if the file already
exists on the client?
Click to expand...

Scripts.

Can you write a script to do this?

If so, do so and test it -- then try it from a submitted batch file or
in the GPO directly. (Running it as a submitted job removes the
assumptions you may have about environment or path etc.)

Once that is working, create it withing a GPO, paste in the working
script (easier to get right this way), and assign the GPO.
3) would I be able to set the gpo up in a way that I can set it up once and
leave it?
Yes.

In other words, the .mdb file I need to keep up to date on the
clients can change as often as once a week (filename remains the same of
course).
Click to expand...

Actually it could change as often as you wish (depending on
size and performance) and it could just work.

xcopy /d \\server\share\database.mdb c:\data\directory

/d will update based on date and time stamps.

One warning about MDB files and Access though: everytime they
are opened they change the last used time on the file and so in effect
it is a "new" version.
Can I simply create a gpo once that points to the location of the
file to copy so that all I need to do is copy over (overwrite) that file
with the new one and do nothing else?
Click to expand...

Watch out for permissions, paths etc, but yes. Probably best
to link this to the COMPUTER container if you can guarantee
the computer will boot, as the STARTUP script.

Also consider if this makes more sense as a RECURRING
task -- run on a schedule (e.g., at night) even if the machines
don't reboot and the user stays logged on????
 
Thanks for the reply. I appreciate all the input. I accidentally left out
one key point. That is that a decision needs to be made as to whether a new
file is available or not... If there is a new file, then copy it. I have
been accomplishing this via a login script. The login script is a WSH
vbscript that actually opens the local database file to check for a version
number, then opens the database file on the server to compare the version
numbers... if the server contains a higher version number then it updates.
It works very well but I am interested in finding out how GPO's can to
this... I spent a lot of time creating this script (it does several things
including seting up necessary directory, shortcuts, and some registry
modifications, if they are not present), and thats one of the reasons I was
wondering if AD's GPO's may have been a better choice to begin with. Plus I
just like to learn and explore other methods.

It seems from your suggestions that even with GPO's, my own script would be
required. correct? I guess what I was looking for the GPO to do was provide
a way to just assign a file to client machines. To ensure each machine had
this file. And to somehow know when to re-copy, ie, new version present.
Maybe I could create my own msi for this? but even doing that what are my
options with GPOs with regard to knowing 'when' to copy the new file...
still need my script? or would I just leave out any decision making
functionality and simply enable/disable a GPO with a simpler script, or
package, when necessary? hmmm... dunno. Another reason for wondering about
this is I want to know if what I had done is way overkill and if GPO's could
have provided a much simpler, more elegant solution.

thanks again... any other input is welcome.
 
djc said:
Thanks for the reply. I appreciate all the input. I accidentally left out
one key point. That is that a decision needs to be made as to whether a new
file is available or not... If there is a new file, then copy it. I have
been accomplishing this via a login script.
Click to expand...

Well, ok, but I answered that anyway: xcopy /d

XCOPY /d only copies files if they have changed or don't exist
on the destination.
The login script is a WSH
vbscript that actually opens the local database file to check for a version
number, then opens the database file on the server to compare the version
numbers... if the server contains a higher version number then it updates.
Click to expand...

Ok, so as long as you can script it this work.

You could also use various "flag" file tricks and
such but what you have seems to work.
It works very well but I am interested in finding out how GPO's can to
this...
Click to expand...

By running the script as the STARTUP script would be the
obvious way.
I spent a lot of time creating this script (it does several things
including seting up necessary directory, shortcuts, and some registry
modifications, if they are not present), and thats one of the reasons I was
wondering if AD's GPO's may have been a better choice to begin with. Plus I
just like to learn and explore other methods.
Click to expand...

Probably not (except by running the script.)

It seems from your suggestions that even with GPO's, my own script would be
required. correct?
Click to expand...

Yes, as part of the GPO.
I guess what I was looking for the GPO to do was provide
a way to just assign a file to client machines. To ensure each machine had
this file. And to somehow know when to re-copy, ie, new version present.
Click to expand...

MSI -- but you would have to create and assign the
MSI packages, and updates to the GPO on each change.
Maybe I could create my own msi for this? but even doing that what are my
options with GPOs with regard to knowing 'when' to copy the new file...
still need my script? or would I just leave out any decision making
functionality and simply enable/disable a GPO with a simpler script, or
package, when necessary? hmmm... dunno.
Click to expand...

Yes, but MSI-GPOs might be extremely tedious to create each
week and offer an overly complex solution.

The script is basically the best way -- from what you have described.
Another reason for wondering about
this is I want to know if what I had done is way overkill and if GPO's could
have provided a much simpler, more elegant solution.
Click to expand...

Probably would be the other way around.
 
Thanks Herb. I appreciate your input.

Herb Martin said:
Well, ok, but I answered that anyway: xcopy /d

XCOPY /d only copies files if they have changed or don't exist
on the destination.
updates.

Ok, so as long as you can script it this work.

You could also use various "flag" file tricks and
such but what you have seems to work.


By running the script as the STARTUP script would be the
obvious way.
Plus

Probably not (except by running the script.)



Yes, as part of the GPO.


MSI -- but you would have to create and assign the
MSI packages, and updates to the GPO on each change.


Yes, but MSI-GPOs might be extremely tedious to create each
week and offer an overly complex solution.

The script is basically the best way -- from what you have described.


Probably would be the other way around.
Click to expand...
 
Back
Top