Ok, having an issue that I have seen several threads on but no real conclusion to the other threads.
I have approx 20 workstations running Windows 7, XP, & Vista. At this location we only have a workgroup, NOT a domain. Each workstation has a standard user configured with no password, and also an admin user with a password. I set up my Console with the install package, and a new deployment task. In the deployment task I set the username and password of the admin account on the workstations with our workgroup name as stated in the user guide. I’m getting “error 5 (Access is denied)” after my username in the log. I’ve tried several suggestions that I found on other threads but I’m missing something and can’t put my finger on it.
My admnin on each workstation has full rights, password is good, I’m at a loss.
I have no third party firewalls, or other AV software on the workstations.
The reason is because it doesn’t work that way. there is no “workgroupname\username” user. It only works that way in a domain environment.
In order for it to work the way that you want, you’ll have to put “machinename\username”. As you might suspect, that will be different for each machine, so the install will have to be different for every computer.
Another reason to use a domain instead of a workgroup in a business environment. Securty gets a LOT easier.
An easier way to do it is to create an .msi package and distribute it to all computers and install manually. Not the best solution, but a solution nonetheless.
If you can, I’d make a point to get a domain controller in there eventually.
Oh beleive me, I’ve been pushing for a Domain at this site. I’ll get it eventually, but until then… Thanks for the help. I’ve noticed alot of issues related to simple file sharing from previous versions, has that been solved with windows 7 or can that still play into it?
It definitely can play into it, but this is just a plain old permissions issue. A general “workgroup\user” account can’t exist, because there is nothing to authenticate, create, or contain that user. That’s where the server \ domain comes in. Workgroups are horrible in businesses, and it’s just going to make something like this A/V roll-out way more painful than it should be.
Good luck to ya on getting that DC soon. SBS servers are pretty nice, and fairly easy to use. It should be perfect for a 20 computer domain.
No, basically you just need to keep the AMS on one computer with a static IP address. Then all the computers will download their updates from it. I didn’t read up on creating MSI packages, because I’ve never had to, but I assume that during the creation of it, you can put the IP address of the AMS server in there. If not, then you just have to make sure that the IP address of the AMS mirror is correct in the properties of the “Computer Catalog” in the ADNM console.