Again, no experience. I do have WinSer2003 on one partition. Seldom use it.
I would make sure that all machine son the LAN have an identical
Administrative account. you should check this account in duplex mode. You
should make sure that your server sees some crucial folders in Vista and
vice versa. You should make sore that you can un some jobs on network like
printing.
Then you can try to poke the system in terms of changing sensitive nodes,
like setting up an account on WinSer2003 and removing it and vice versa.
The components are a different ballgame. They do not seem to have an
identifiable API although you may look for it.
I would go to Windows\System32 in Vista and examine ALL execs like calc.exe,
alphabetically. Obviously calc.exe is not what you need. I would do it by
typing dir a*exe to get all execs starting with an "a".
Let's you've got a list of all a's. Here it is:
11/02/2006 04:44 AM 81,408 ACW.exe
11/02/2006 04:44 AM 38,400 AdapterTroubleshooter.exe
11/02/2006 04:44 AM 58,880 alg.exe
11/02/2006 02:09 AM 12,498 append.exe
11/02/2006 04:44 AM 19,968 ARP.EXE
11/02/2006 04:44 AM 24,576 at.exe
11/02/2006 04:44 AM 28,160 AtBroker.exe
11/02/2006 04:44 AM 16,384 attrib.exe
11/02/2006 04:44 AM 88,064 audiodg.exe
11/02/2006 04:44 AM 41,472 auditpol.exe
11/02/2006 04:44 AM 640,000 autochk.exe
11/02/2006 04:44 AM 653,312 autoconv.exe
11/02/2006 04:44 AM 632,320 autofmt.exe
11/02/2006 07:34 AM 57,856 AxInstUI.exe
14 File(s) 2,393,298 bytes
0 Dir(s) 36,247,041,024 bytes free
then you go thru the list and say:
alg.exe /?
This is supposed to give you the help.
Some of them are legacies from XP or earlier OSs and are useless, you won't
get any help.
There is a chance you will find an API that can change Windows components in
Vista. Most likely you will.
You will have to set the parameters thoughtfully, of course.