Installing ePolicy Orchestrator 3.0 on the same server as SQL Server 2000

  • Thread starter Thread starter Ryan Cabanas
  • Start date Start date
R

Ryan Cabanas

I'm planning on installing ePO 3.0 on the same server as SQL Server
2000 is installed on, but I was reading the manual before we get the
product. I was reading through the Installation Guide and on Step 12
it talks about how to set up ePO for it to log onto the database
server. If I'm installing it "on" the database server, what should I
choose, NT account, or SQL Server account? Thanks for the help.

Ryan Cabanas
 
Ryan Cabanas said:
I'm planning on installing ePO 3.0 on the same server as SQL Server
2000 is installed on, but I was reading the manual before we get the
product. I was reading through the Installation Guide and on Step 12
it talks about how to set up ePO for it to log onto the database
server. If I'm installing it "on" the database server, what should I
choose, NT account, or SQL Server account? Thanks for the help.
Click to expand...
Hy,

first install EPO 3.0.1 instead of 3.0
Use a SQL server account, so you can change it in future without problems.

Bye, Giuseppe
 
Giuseppe,

Thanks for the reply. Okay. I will do that. We haven't recieved our
copy of ePO yet, but I believe it will be v3.0.1. Thanks.

Ryan Cabanas
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

EPolicy Orchestrator 3.0 error w/ UNC repository 0
How to change the IP ports which MS-SUS uses on a server? 1
SQL Server 2000 9
Installing SQL Server 2008 Express with BCM installed 3
SQL Server Express 2008 - missing service 1
Install WSUS 3.1 on x64 Windows Server 2008 datacenter failed. 1
Access 2003 & SQL Server 2000 3
Error while trying to establish connection to SQL Server from MSVS2008 7

Back
Top