Heeter

Hey all,

Would like to know what you guys do about software that doesn't install nicely through a server.

I got some software (Quickbooks, Simply Accounting, etc) that didn't come with .msi files, and they aren't working properly for the users in the domain, unless they have full admin privileges.

Any thoughts?


Heeter

madmatt

Store it on the server and go around desktop to desktop and install it from the share.

---

Heeter

Thanks Matt,

That's what I ended up doing with a couple of them. Now that you mention that, I think that I am just going to keep all the cd images on the server.

Heeter

kcnychief

^That's what I do, works well. Master CDs are all kept offsite for DR reasons

---

Heeter

But it is frustrating in that these pieces of software are not working well in a domain setup. they are intended to work in a stand alone machine. When the user logs on, the software only works partially. Some won't take updates from the software manufacturer site, even though I assigned the user as a power user on the workstation.

Oh well, I think that I need to vent, thanks for listening to me out. Maybe I have to rethink how I am setting up the workstations...............





Heeter

LordOfLA

Power users don't get anywhere near the permissions needed for software updates to work

---

Heeter

If I set them up as administrator at the workstation, not in the Server, won't the user be able to install software on the workstation at that point? This is what we are trying to avoid, because of previous history.



Heeter

LordOfLA

Yes. But nobody has ever yet justified not giving admin rights to workstation users given that 99% of windows and windows software assumes that all users have admin rights. This in turn creates unnecessary work and preventable issues when you remove those rights from users.

---

kcnychief

Heeter - what I typically do is give people admin rights for the first two weeks after a new PC or New Workstation setup. I don't really let them know, I more simply make sure the station is setup for thier job needs. If I know for sure it is beforehand, or after the two weeks I drop them down to normal users.

It's a happy medium you have to find, best of luck.

---

omg its nlm

I use AutoPatcher and make my own modules.

---

madmatt

I would never, ever use AutoPatcher in a network environment, e.g. a business network.

---

Heeter

Thanks, D.

I think that will be going this route. I will upgrade their status to admin on the workstations. then will drop them back to power user afterwards.

I am doing some research on the various software that I am dealing with. I have found that one of these pieces of software can work in a terminal server environment with a whole swack of configging needed.

I think that I might present the boss of this company this idea and see if he let's me test drive this. I think that this boss is getting frustrated at how slow the transition is from a 10 year old workgroup setup with each machine being so buggered up from spyware and viruses to this new domain setup.

Anything of the top your guys heads that I should watch for?

Thanks a million for all you guy's inputs, really much appreciated.

Heeter

kcnychief

Each environment is unique, not much you can really do to plan ahead of the unknown. If you manage multiple environments, I recommend using the same "flavor" of Windows Server, and design your IP schemas, OUs and everything else the same. Makes everything much easier

---

madmatt

I agree to a certain extent. The first portion depends on what the job calls for. Some small businesses can't afford two servers which makes Small Business perfect, especially for those who want Exchange.

However, I agree with the second half of that statement. =]

---

kcnychief

Good point as always Matthew

---