Link to home
Start Free TrialLog in
Avatar of sam15
sam15

asked on

Admin Account on Windows 2016 Server

I have a crystal reports server 2016 installed on windows 2008 server under user "admin" . I and other admins  use that account to login into it.

We are migrating to a new windows 2016 server. The new machine was  built with my user name which has admin privileges.

The data center told me they stopped creating a shared "admin" account and I can install the crystal server using my account.

I can also create myself an "admin" account on machine.

Is there a common practice for this ? Shall i install the crystal server using my account or create a new account named "admin" and use that?

Thanks..
ASKER CERTIFIED SOLUTION
Avatar of McKnife
McKnife
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Consider having two accounts for every admin user, one privileged admin account, and one regular user account.  The regular account is used primarily and access can be elevated whenever necessary. Perhaps you need admin to install only and not necessarily run the software at all times.  Either way, there shouldn't be any shared accounts in use.
Avatar of sam15
sam15

ASKER

so in conclusion there is no benefit or need for me to create a second "admin" account and install crystal server using that account.
I can just use my own name existing account that has admin privileges to install crystal server. Is this correct?


SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sam15

ASKER

so even though crystal server is installed under my account, if another admin logged in using his own account he should be able to see the crystal admin tools and everything else as I do?
Sure.
Some software will explicitly ask whether it should be installed for all users or just for your user, but if it does not ask, it is installed for all.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Never needed to use the built-in administrator ever in 20 years of server administration.
Privileges are the same for members of the admin group and for administrator (that is, if we speak about the privileges that you can list by using the elevated command whoami /priv). All there is different, is that the built-in administrator does not have to elevate (UAC does not influence that account at all).
Mike, what promotion from DEV to TEST to PROD do you mean?
Avatar of sam15

ASKER

It seems there is some difference between named account and internal ADMINSTRATOR account.

I installed the crystal server using my own admin account but when i tried to edit tomcat config file or write files to folder under C:\program Files the system said i Need admin privileges for that.

I told windows admin about this he did some registry change and reboot so i can dont get the message again.
He said he had to set some local policy for my account.

I wonder if windows admins dont give the internal windows ADMINSTRATOR account to application admins and leave it to be used by themselves.

The effect you saw is because of UAC. All admins but the built-in account administrator need to elevate. That is expected and ok. So to edit files in protected locations like program directories, you need to elevate the program you do the editing with. Right clicking the executable, you need to select "run as administrator".