Discussion Locked

SMS SP2 question continues....

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Damn character limit...

domain admins complete successfully (as expected,) but our regular users fail because they still don't have access to the files (by design.)

The only two methods I can think of to solve this are: (1) Set up an SMS Installer program that we can push down to the clients that just copies the files from the archive, or (2) place the files on a share point with the permissions Everyone/Full Control. 1 seems like a lot of work, and 2 is a security no-no for our organization.

Does anyone have this same problem and a solution?

2 replies

by mckaytech

We are involved in the SP2 dilemma but on a much, much smaller scale. However, I think your solution #1 is workable and in your environment, probably the preferable approach.

But in regards to #2, does the share point really have to be full control or could it be read-only and would that make any difference to your security policy?

regards!

paul

by erikthered

Thanks; it ended up being #2. The error was in the batch file I wrote...it was mapping the C$ share on the workstations as a *regular user*! No wonder it didn't work. I didn't change the file when I changed the context in which the package runs fromadmin to logged-in-user.

This discussion is closed to new replies.