Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Microsoft Client
 | |
|
- Cancel Connection Information
- Change NT Password from Win95 Machine
- Change User Rights
- Create a List of Available Workstations
- Deleting Orphan Shares
- Determine if 95 User is Logged into a Network
- Determine if a Server is a PDC
- Determine if a User is Connected to a Server
- Determine NT Admin Rights
- Display a policy statement before logon
- Distinguish between NT 4 Server and Workstation
- Enable MSClient
- Get a List of Attached Servers to NT Server
- Get NT Users Primary Domain
- Get remote user name
- How to Create NT Groups
- How to Get Domain Controller of Authenticating Server
- Install apps on NT without system admin priviledge
- Itemize Network Services
- List Members in an NT Domain
- List of Users Who Have Group Access
- Listing Hidden Shares
- Look up Access Permissions to an NT Resource
- Map Drive to NetLogon Share Handles Z Drive
- Map Root and Map to Share under NT and 95
- Network invalid error
- NTFS - POSIX subsystem and Case Sensitivity
- NTFS Detection
- Only Map Drive when Its Not
- Refresh Group Policy using SecEdit
- Remove Workstation from a Domain
- Retrieve a List of Computer Accounts on NT Domain
- Set up User with Grant DialIn Permissions Set
- UDF -GetUserNameEx
- Why Do Certain Win32 Apps Misbehave in NT Services
- WWNET32I Extender with Older WinBatch
- wxxFileUsers Functions
- wXXGetUser and Netname
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Install applications on NT without system admin priviledge
Keywords: wntRunasUser remote installation
Question:
Can you give me any pointers on how to install applications remotely?Answer:
Well, I'll first create a winbatch script to install an application, and test it, etc. Then I'll zip up the installation files, and push these out to various NT machines via the administrative shares on the target machines (C$, etc.). Then, I'll use the AT scheduler to schedule that script to kick off at a certain time on that remote machine. AT (the schedule services) allows for scheduling on remote machines. Because the schedule service is running as the system account, the script runs with privileges above what the user has (our users are typically given power user privileges).Occasionally, this won't work, because the install requires a "real" user, or needs "real" administrative privileges, and I've begun to use the new wntRunasUser in this instance to switch from the system account to a real user account. This, however, is the exception rather than the rule. The system account can do nearly anything on an NT machine that an administrator can do.
Article ID: W14261
Filename: Install apps on NT without system admin priviledge.txt
File Created: 1999:10:26:11:22:54
Last Updated: 1999:10:26:11:22:54