It's the installation that needs Admin rights. Once installed, it will use a LocalSystem account for the services.
To install this w/ admin rights even if a guest account is logged in, customize the agent install from the ePO console. Right-click on the directory, then select "Customize Agent Package". Here you can "embed" an admin account to be used just for the installation. That account will not be used for any other function.
HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation
You can always create MULTIPLE Agent installers, right? Just rename the agents to the correct domain then you should be fine. You can sort this out from a login script something like this:
if %DOMAIN%=Domain1 then AGENT_DOMAIN1.EXE
if %DOMAIN%=Domain2 then AGENT_DOMAIN2.EXE
.
.
.
You get the drift?
HTH, AVChap
... my $1 worth of advise, 2cents isn't enough due to inflation
Just planning out a test of ePolicy in an Enterprise environment. Numerous small offices participate in workgroups only and don't run logon scripts. My first thought was to add a local admin account to all machines but the security group was concerned about the one user/password fits all scenario. Never thought about creating multiple Agents.
I am have't domain, but I have same account with same password in all workstations.
All users exits in Novell Directory Services.
Can I make installation package with administration privileges to run on WindowsXP?
I am have't domain, but I have same account with same password in all workstations with administration privileges.
All users exits in Novell Directory Services.
Can I make installation package with administration privileges to run on WindowsXP?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.