Login

[WXP, FMD7]

The startup script in one file executes a script in another, which
simply updates certain future dates in that file for lookup later. Both
files are set to open as user "Admin". Up to now, all has worked
perfectly.

Suddenly, the second file has been opening in some sort of alternate
user reality, telling me that certain operations (Set Field steps in
the script) cannot be performed because the file is not modifiable.
Setting a field with Get ( AccountName ) confirms Admin is in fact the
user, but for some reason I am locked out of any modifications,
including ScriptMaker and Layout.

I can open the second file directly without any problem: no issues with
the update script. It would thus appear to have something to do with
being called from the first file, but what? I have changed nothing, and
there are no scripts which do anything to alter the user or privileges.

I can insert a Re-Login step (as Admin) in the script which is executed
in the second file. This works around the problem, but I hardly believe
it should be necessary, especially since everything worked perfectly
before without it.

Any ideas?

Matt
.

Relevant Pages

  • Re: slow logon
    ... in the logon time have been reduced so far. ... update the time for the clients that talk to the dc as the logon server. ... start up script in AD to apply updates to the clients machines which is ...
    (microsoft.public.windows.server.active_directory)
  • Re: slow logon
    ... that i tell the software not to restart the services when new virus updates ... update the time for the clients that talk to the dc as the logon server. ... > We have a Start up script and a login script for users as well as> folder ...
    (microsoft.public.windows.server.active_directory)
  • Re: slow logon
    ... > we have symantec av 10 and yes the software looks for updates from a> local ... > i told the programmer that the domain controller at each site will> check ... > update the time for the clients that talk to the dc as the logon> server. ... >>> We have a Start up script and a login script for users as well as ...
    (microsoft.public.windows.server.active_directory)
  • Re: slow logon
    ... DNS is AD integrated and we have dhcp servers ... All clients are XP pro sp2. ... Not everyday is updates applied ... Make sure that the script detects if that update already has been made, ...
    (microsoft.public.windows.server.active_directory)
  • Re: slow logon
    ... that i tell the software not to restart the services when new virus updates ... i noticed that the login script created by the programmer has: ... update the time for the clients that talk to the dc as the logon server. ... start up script in AD to apply updates to the clients machines which is ...
    (microsoft.public.windows.server.active_directory)