![]() |
| |||||||
| Notices |
![]() |
| LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) |
| How can we detect for Windows Vista in our Logon Script? Previously we could use OSVER.exe or even a 3rd party app OSVER61.exe to detect all versions of windows through Server 2003. When OSVER is run on Vista it returns nothing, not even unknown, just nothing. Is there a way to detect if a user is running Vista or not? Maybe a newer version of OSVER, or another command that we can run in a batch file? TIA | Guest
Posts: n/a
|
|
| | #2 (permalink) | |
| Just like before, Control panel -System "Dave" <Dave@discussions.microsoft.com> wrote in message news AC8245A-41B5-460E-8C1E-7AD8B9DA043D@microsoft.com...Quote:
| Guest
Posts: n/a
| |
|
| | #3 (permalink) | |
| "Dave" <Dave@discussions.microsoft.com> wrote in message news AC8245A-41B5-460E-8C1E-7AD8B9DA043D@microsoft.com...Quote:
Ex - if %os%==Windows_NT then do winxp stuff (as we have no nt4 or even 2k pro machines on the network, this worked properly) For Vista, I noticed that the %os% variable is the same, so I had to check something else, but I needed to do this before my xp check, so now I do something like this... if "%allusersprofile%"=="C:\ProgramData" goto WinVista if %os%==Windows_NT goto WinXP :: ::if it gets here, assume 9x base :: exit :: :Winvista @Echo Windows Vista Operating System Detected goto fin :: :winxp @Echo Windows XP Operating System Detected :: :fin This is an example of a script I use daily, and I've not yet had a problem with it detecting the wrong OS. Hope this helps. D | Guest
Posts: n/a
| |
|
| | #4 (permalink) | ||
| D, Thank you, that's EXACTLY what I was looking for. -Dave "D" wrote: Quote:
| Guest
Posts: n/a
| ||
|
| | #5 (permalink) | |||
| "Dave" <Dave@discussions.microsoft.com> wrote in message news:325968FA-2FA5-4115-9E84-35D21E54B2DD@microsoft.com... Quote:
Glad to help out. Doug | Guest
Posts: n/a
| |||
|
| | #6 (permalink) | |
| Hi, here is the code I used in my batch File: ECHO *Detecting Windows Version... VER | findstr /i "5.1.2600" > nul IF %ERRORLEVEL% EQU 0 GOTO XP VER | findstr /i "5.2.3790" > nul IF %ERRORLEVEL% EQU 0 GOTO 2003 VER | findstr /i "6.0.6000" > nul IF %ERRORLEVEL% EQU 0 GOTO VISTARTM :XP ECHO *Windows XP REM TODO GOTO EOF :2003 ECHO *Windows Server 2003 REM TODO GOTO EOF :VISTARTM ECHO *Windows Vista RTM -- Thanks æ*‘ 大家有时间å¬ä¸€ä¸‹ã€Šé›ªèŠ±ã€‹ "Dave" <Dave@discussions.microsoft.com> wrote in message news AC8245A-41B5-460E-8C1E-7AD8B9DA043D@microsoft.com...Quote:
| Guest
Posts: n/a
| |
|
| | #7 (permalink) | ||
| Thanks Youyang, I'll keep this one in mind also. We might be pushing our luck here, but does anyone have an idea on how to determine the "flavor" of Windows Vista? We probably don't want to run the same commands for our users who have Vista Home vs. Business/Ultimate. -Dave "youyang" wrote: Quote:
| Guest
Posts: n/a
| ||
|
| | #8 (permalink) | |||
| I don't have Vista home on a machine nearby, but on Vista Business (and probably Ultimate and Enterprise), there are 2 variables - USERDOMAIN and USERDNSDOMAIN. So, using the info I orginally posted, and assuming you were on a domain, you could do something like... if %userdomain%==mydomain goto vistabiz or even... if "%userdomain%"=="" goto nodomain ::do vista business stuff here... :: goto fin :nodomain ::system not on domain, so assume vista home :: :fin One thing you can do to see what environment variables to use would be to open a command prompt and type in SET and hit enter. If you have a Vista Home machine near you, compare the variables to see what is on the Vista Home machine that might not be on the Business machine, or vice versa, and then use that variable in your script. Also, you could talk to whomever is resonsible for imaging and deploying machines in your location and ask them to set the machines up with a global environment variable via the default user registry, but I think you'd be better off looking at the existing environment variables. Again, hope this helps. Doug "Dave" <Dave@discussions.microsoft.com> wrote in message news 4B7C136-F21F-40E6-A9C0-4E2BE79BF1B6@microsoft.com...Quote:
| Guest
Posts: n/a
| |||
|
| | #9 (permalink) | |
| D One minor suggestion. Rather than hard coding the drive letter (which fails on my dual boot xp/vista machine with Vista on D I would do it thisway. if "%allusersprofile%"=="%HOMEDRIVE%\ProgramData" goto WinVista Quote:
| Guest
Posts: n/a
| |
|
| | #10 (permalink) | ||
| That's a good idea, but in an AD domain based environment, that might not work as many admins populate the map home drive (letter) to (path) which then sets the %homedrive% variable. But, like I said it's a good idea to not code the drive letter. Instead, and I believe this is what you had meant to say, was to use %systemdrive% Thanks for the tip though Doug "GTS" <x@y.net> wrote in message news:ukSD3o$dHHA.4688@TK2MSFTNGP04.phx.gbl... Quote:
| Guest
Posts: n/a
| ||
|
![]() |
| Tags |
| None |
| Thread Tools | |
| Display Modes | |
| |
| ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| IE7 detect protected mode in script | Ty | Windows Vista Security | 4 | 11-13-2006 04:36 AM |
| Allways allow logon-script | Jesper Hauge | Windows Vista Administration | 1 | 10-09-2006 04:32 PM |
| Unable to run vbs logon script | Wajinga | Windows Vista Administration | 1 | 06-13-2006 09:01 PM |
| VPN and logon script | amer | Windows XP Work Remotely | 1 | 10-02-2003 12:57 AM |
| XP Client using Logon script on NT4 domain | Paul | Windows XP Network & Web | 0 | 06-30-2003 01:48 PM |