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.
Changing Windows 95 Passwords via WinBatch
Keywords: change password
Question:
Do you have any ideas on how to change passwords in Windows 95?Answer:
It is an interesting question. While I haven't put any work into it at my workplace, I've toyed with the idea and here are a few of my musings.As much as possible, we encourage our users to blank out the Windows 95 password on their workstations. This is done by having the Microsoft Client for Networks installed on their workstations (NT authentication usually requires it). Then delete the appropriate .pwl file in the windows directory, and on next login, make sure they put in a blank password. This occurs at the "please confirm your password. This will be used as your windows password" dialogue. The windows password will not ever be out of sync with other passwords for that username again.
Here are the steps:
- Go into control panel and select passwords then select change windows password, and
type in your old password and leave the new password editbox blank and hit ok.
- Next time you reboot you will not be asked for a password.
- If you are wanting to do this in a script then use control manager and sendkeys.
The other musing I have had is to create a local service on each workstation. (this works only for people who usually use the same workstation day-to-day), and on those workstations, have a Winbatch program in the Startup or under Run in the Registry. It would use a registry date counter that would be set to something like a few days before the Netware password expiry date (to allow for weekends). When that date comes up, it would ask the user for his/her new password, and then set about sending commands to the various servers they log into or authenticate to. It may also be possible to check it against a file on a server that has the last-changed dates, or to run a network function to determine the lastchanged date so that it does not matter where the user is logged in from. (this latter idea has the most merit, as it may accomodate users after a length vacation or sick leave).
just a few thoughts. Merry Christmas '97.
Article ID: W13475
Filename: Changing Password in Windows 95.txt
File Created: 1999:04:15:16:54:16
Last Updated: 1999:04:15:16:54:16