"Bert" <Bert@newsgroup> wrote in message
> Hi. I have made a logon.cmd file and put it in the Logon window in GPO.
> I manually run it, it adds the login information of the server. I can
> to the logon.log file from clients and even run a command from the command
> echo "testing1" >> \\server\logons\logon.log and that works where server =
> server name and logons is the share.
> It seems the only thing that isn't happening is when a user logs on, it
> isn't running the logon.cmd file in Group Policy.
> Any suggestions?
When you say you put the file in the logon window in GPO, do you mean that
you physically copied it into the physical location of the GPO after you
clicked on the Browse button? When you click on browse, it first puts you
into the GPO's location in Sysvol.
Normally an easy way to get a file into where logon scripts belong in a GPO,
is after you click on browse, go to another explorer window, go to the
location that your copy of logon.log (was that the name of it? - your UNC
example shows logon.log, not logon.cmd) or where logon.cmd exists,
right-click and copy it, then go back to the GPO logon file browse window,
and paste it in there, then once pasted, select it for your login script.
I assume there are no event log errors on the client side or the SBS side,
as well as that the client and SBS are only configured to only use the SBS'
IP as a DNS address (meaning there is no ISP's DNS, router as a DNS address,
or some external DNS server in their IP properties).
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
for regional support phone numbers.