Database Search
TechHome
 | |
| |
| |
| |
| |
| |
|
- !!Users, Workstations, Domains and Machine Domains Explained
- 1932 Winexec when Opening MultiUser Files on a Network
- 523 Error Enumerating Network Resources
- App not Launching from Mapped Root
- Backslashes with Servers - Volumes - Directories
- Changing Password in Windows 95
- Client IP Configuration script
- Connect to Servers via DOS batch files
- Detect Existence of Client32
- Determine if a Tree of Directory is Mappable
- Determine if a User has Admin Rights
- Disable NetBIOS over TCPIP
- Disconnect Mapped Drives Ex Dialog
- Display a Banner or Message Box on Remote PC
- Find out what Drive Letter is Mapped to Server
- Find Users Logged on Other Machines
- Finding and Listing Processes on Remote
- Getting Currently Connected Usernames to NT Share
- Global Net Map Setting
- Hiding Drive Mappings
- How do I see Im logged on
- Installing your Network via Windows Setup
- Is Network Alive
- Log Off User after an Amount of Time
- MSIE Proxy Server Control
- Net Use Command and Passing Passwords
- NT to Novell Translator
- RASSAPI.dll not Found
- Remote Launch of Winbatch
- Replication Manager - Replicate BDCs
- Sample Code Extracts Authenticating Server Name
- Segment Load Error
- Send Messages to Users
- SNMP in WinBatch
- Test Network Drive Mappings
- Unexpected Network Error
- Update All NT Existing-New User Registry Configs
- Use of Newer Network Extenders with Older Winbatch
- Using a BAT File to Launch Subsequent Operations
- Validate a Userid and Password
- Wake up Machine on LAN
- Who is Logging on to Remote NT Server
- Win32 Network Errors
- Workaround for Network Error 510
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Detect Existence of Client32
Keywords: Detect Existence of Client32
Question
I am looking for a quick and easy way to query the registry to find out if Client32 is installed on a particular PC. Any ideas??Answer:
Look for some of the following information in the local machine registry: REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NOVELLNP]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NOVELLNP\NetworkProvider] "Name"="Novell_NetWare" "ProviderPath"="novellnp.dll" "Description"="Novell NetWare Provider for Windows 95/98" "NetID"=hex:00,00,03,00 "CallOrder"=hex:00,00,00,20 "GroupFcn"="NWGROUP.DLL,NWGetUserGroups" "NovellDirectoryServices"="Novell Directory Services" "NetWareServers"="NetWare Servers"
I think that looking for [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NOVELLNP] is probably the most accurate method at this time. Of course, if the installation of Client32 is damaged in some way then you could be missing files or registry entries and thus might get a false positive or negative result for your testing depending on the method that you use to detect Client32.
Article ID: W14469
Filename: Detect Existence of Client32.txt
File Created: 2000:05:04:12:54:44
Last Updated: 2000:05:04:12:54:44