Customer has Pro-Services coming onsite. Prior to them arriving they are trying to ensure all the required access / port / firewall rules and accounts are all created. Is it possible to set up the DB without setting up ePO???
No. You can setup SQL and its associated port, instance, firewall rules, and access accounts but no you can't create an EPO database for installing EPO.
So there's no way to create a sql DB and then during ePO setup point it to that DB?
Customer wants to make sure all permissions and port communications for the DMZ server and access for the DMZ accounts are present and correct prior to McAfee being on site.
Apparently a competitor, has the option of setting up a DB ahead of time and just pointing their product to it.
I am hoping McAfee SQL support can give me a similar process that we can do prior to running the installation of ePO and we can simply point the installer to the pre-created empty Database.
The EPO database is created by the application installer and is tied to the EPO file system associated with it. There would be no need to create a database first as long as whoever installs SQL knows what they're doing. Just follow our KB for Ports-required and SQL-permissions-required and you should be fine.
The only way you can point to an existing database is when you are trying to do an install from the backup located in the DB files or doing a crash recovery the old fashion way. The DB creation is fast when doing the install. Even if you just created the container DB, there many tables, index, stored procedures and those are tightly linked to the install.
Structure and content are created by the product and are tightly integrated. But you can move an epo database with its application server, if IP or name change you follow the crash recovery process.
For your specific issue, I gather from what you are saying to get everything ready, if you have both the db server and the app server up, you can create a database on the sql server and see if it is accessible by the app server. That should be enough to test your connectivity issue (create a .udl file and fill the blanks)
Refer to the following for the permissions required by the ePO SQL account: