cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Harveys
Level 7
Report Inappropriate Content
Message 1 of 3

initial ePO installation without domain controller then moved onto Doman.

Jump to solution

Hi,

We are looking to build a Windows 2016 Server with ePO 5.10 Patch 12 off site and then when we install on site bring it into the domain.

Initially the server will be a workgroup server with a static IP address (which will not change when attached to the domain)  we will also install a local copy of SQL on the box.

Is this possible?

We would also like to install the agent onto the workstations prior to the server going live on the domain, we  know the agent will give errors until the server is up and running but again will this work given the Agent would have bee created prior to the server being attached to the domain? 

 

Many thanks in advance for your assistance.

1 Solution

Accepted Solutions
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: initial ePO installation without domain controller then moved onto Doman.

Jump to solution

It would be best to have it on the domain to start with.  If you add it to the domain, that will change the system name (fqdn) and that will break sql.  Also, you would need to ensure dns resolves properly.  As far as epo goes, if netbios is staying the same and dns resolves to that host after it is joined to the domain, the agents should be able to connect.  

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a-...

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

View solution in original post

2 Replies
cdinet
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: initial ePO installation without domain controller then moved onto Doman.

Jump to solution

It would be best to have it on the domain to start with.  If you add it to the domain, that will change the system name (fqdn) and that will break sql.  Also, you would need to ensure dns resolves properly.  As far as epo goes, if netbios is staying the same and dns resolves to that host after it is joined to the domain, the agents should be able to connect.  

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/rename-a-computer-that-hosts-a-...

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

aguevara
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 3

Re: initial ePO installation without domain controller then moved onto Doman.

Jump to solution

also, (aside of the SQL concerns) if the FQDN from the server changes and there are agents already communicating to it then it is indeed important to retain the IP address as the Agents will attempt to communicate to the server's FQDN, NETBIOS and last it IP, if the first 2 fail then they will succeed with the IP and retrieve the new server FQDN.

Its very important to retain one of them, the FQDN or the IP, so never change both at the same time 🙂 

Regards

Alejandro

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

 

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community