are VBscript on Windows server 2003 and VBscript on WS2008 compatible?
in [VbScript]
|
From: Francois Lafont on 25 Apr 2010 14:21 Hi everybody, Sorry if my question has already been asked, but I haven't found anything which is clear for me on this point. I spent a lot of time learning VBscript on Windows server 2003 (my sources are script56.chm and script_center.chm files), especially VBscript for using Active Directory (creating user accounts etc). Now, I have several scripts and I'm rather satisfied. I would like to know if my scripts will always work on Windows server 2008 or if, after migration to Windows 2008, I would have to rewrite my scripts? Thanks in advance. -- Fran�ois Lafont
From: Al Dunbar on 25 Apr 2010 21:09 "Francois Lafont" <francois(a)nospam.fr> wrote in message news:4bd48816$0$24603$426a34cc(a)news.free.fr... > Hi everybody, > > Sorry if my question has already been asked, but I haven't found anything > which is clear for me on this point. > > I spent a lot of time learning VBscript on Windows server 2003 (my sources > are script56.chm and script_center.chm files), especially VBscript for > using Active Directory (creating user accounts etc). Now, I have several > scripts and I'm rather satisfied. > > I would like to know if my scripts will always work on Windows server 2008 > or if, after migration to Windows 2008, I would have to rewrite my > scripts? 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 dependencies. /Al
From: Francois Lafont on 26 Apr 2010 08:07 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 dependencies. Thanks for your answer Al. For example, would this script work well on Windows Server 2008 (it works well on Windows Server 2003)? http://sisco.laf.free.fr/codes/exemple.html 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? -- Fran�ois Lafont
From: Richard Mueller [MVP] on 26 Apr 2010 13:06 "Francois Lafont" <francois(a)nospam.fr> wrote in message news:4bd581f1$0$22046$426a74cc(a)news.free.fr... > 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 >> dependencies. > > Thanks for your answer Al. > > For example, would this script work well on Windows Server 2008 (it works > well on Windows Server 2003)? > http://sisco.laf.free.fr/codes/exemple.html > > 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? > > > -- > Fran�ois Lafont I would expect any script that works with AD and ran fine on Windows Server 2003 to also run fine on Windows Server 2008. After a quick glance, the script you linked seems fine. I believe VBScript is unchanged on W2k8, and AD is the same except for added features. Even permissions issues should be the same in W2k3 and W2k8. A script that accesses the file system or the registry would be another matter, and even here a 64-bit OS compared to a 32-bit OS would be a bigger issue. -- Richard Mueller MVP Directory Services Hilltop Lab - http://www.rlmueller.net --
From: Al Dunbar on 26 Apr 2010 13:07
"Francois Lafont" <francois(a)nospam.fr> wrote in message news:4bd581f1$0$22046$426a74cc(a)news.free.fr... > 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 >> dependencies. > > Thanks for your answer Al. > > For example, would this script work well on Windows Server 2008 (it works > well on Windows Server 2003)? > http://sisco.laf.free.fr/codes/exemple.html > > 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 is that: - 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. /Al |