"Francois Lafont" <francois@newsgroup> wrote in message
> Al Dunbar wrote :
>> That rather depends on what the scripts do. If they run they should do
>> whatever they do now. There could be some issues similar to those found
>> running on vista or windows 7, where the User Account Control has been
>> known to cause issues.
>> In addition, your script may include some inadvertent version
> Thanks for your answer Al.
> For example, would this script work well on Windows Server 2008 (it works
> well on Windows Server 2003)?
> Generally, would the scripts work well on Windows Server 2008, knowing
> that they modidy Active Directory (create/move/delete user accounts,
> change attributes of user accounts) and they already work well on Windows
> Server 2003?
Not having any w2k8 experience I cannot answer definitively for you,
however, I do not think that w2k8 introduces any changed behaviour to the
standard AD objects. The script sample seems relatively clear of o/s version
bias, which is what I was trying to warn you about.
Having migrated vbscripts through other o/s version changes, all I can say
- it is possible to write scripts in one environment in such a way that they
fail in another. Some examples: a w98 script might be written assuming
read/write access to some system folder that is readonly in wxp, or might
have a name hardcoded ("Documents and Settings") for a system folder whose
name is different in another o/s ("Users" in vista).
- it is possible to write scripts in one environment in such a way that the
changes required to migrate to another environment have been somewhat
anticipated and therefore reduced, possibly to zero required changes.
So the answer to your question depends on which category your particular
scripts fall into.