//flex table opened by JP

Click to See Complete Forum and Search --> : Create/mgmt Win NT roaming profiles


rowing2
05-17-1999, 02:02 PM
Hi No Wonder!

Background:
1) We have a Windows NT server/network, 35 WinNT Workstation PCs, and 50 user accounts.
2) All user accounts are WinNT Roaming Profiles (saved on the NT server).
3) An initial script was used to setup the PC and user desktop followed by 7 subsequent upgrade scripts. During upgrades, the user account for the primary user of the PC was used along with an Admin account depending on the specific task in the upgrade (user accounts do not have privs to install software).
4) For a new user and PC, we use a comprehensive script that includes all 8 upgrades.
5) We have 35 updated user accounts. None of the other 15 non-PC-owners have used their accounts (disabled). The 15 users share a common PC, or use any PC that is not in use.
6) All users have a Microsoft Exchange email account and use Outlook 98.

Questions:
1) How do I update the 15 non-pc-owner user accounts to get them equivalent to the upgraded version of the PC-owner user accounts (part of update require Admin account, and part require user account)?
2) Once updated, how do I perform incremental updates for non-pc-owner accounts to match pc-owner account updates as they come along, such as upgrade #9?
3) How do I setup a new employee's account?

Summary:
I need a working process and detailed instructions for managing users, accounts, and PC software updates. I thought that this should be a common process for companies using NT roaming profiles, however our local consultants do not have much familiarity with this.

Any help would be greatly appreciated!!!

Thanks,
Don
Rowing2@together.net

Jin Vitas
05-17-1999, 02:16 PM
use SMS (systems management server)

ANTONIO E GUERRA
05-17-1999, 11:33 PM
I guess you are the administrator of this domain. Upgrade all the workstations using a remote upgrade installation disk. Create a folder in the main server and proceed to upgrade all the other computers. When you are done, establish the profiles and permissions to all the members of the domain.

BBA
05-18-1999, 06:47 PM
I run PC suppport for a company with over 2500 PC's.

In my companies configuration, we use WinInstall Ver 6 distributed thru Novell and NT domains. Each user id has its own profile in domain and in netware. The winstall group memberships for each user will allow the PC to have automatic installation of software for the primary users id on logon (as determined by the %2 variable id in the client settings).

Although any user who wants can log on to any PC (roaming profiles), they can only recieve Email from a PC built with the %2 set to them, unless they manually connect to their user id's pst files into Outlook. The pst's are stored on network drives created for each user, so that only they have access to it from their log-in.

We have generic machines built for temporary employees which have no Email access and each generic id has its own software
installation group memberships so that they too will stay updated with the Wininstalls.

I know your system will be considerably less complicated due to fewer account requirements, but this might still be a good setup for you to consider.

BBA