POS 2009 with SQL Server on Domain Controller

Hello,

In preparation for a POS 2009 installation, I have been doing some tests to make sure the product will work in our environment. I would like to have the primary POS database on our Small Business Server 2008 machine. I don't have a SBS machine available for testing, but I have been testing this with Windows Server 2008 configured as a domain controller.

So far, I've been having trouble setting up the database when the server is configured as a DC. I get the following error after waiting for a few minutes while the DB is set up: Failed to create database MSPOS. Error Details: Failed to create the windows users/groups or add the sql logins.

The database is still created, but it is not usable. If I try to connect to it from a client computer, I get the following error: An error occurred while attempting to create users and groups for Microsoft Dynamics POS. For technical information about this problem, click Details. (Details:) The creation of all Pos groups could not be completed

If the server is not configured as a DC, I have none of these problems. I suspect it is because, as a DC, the server has no local user database. Still, it seems like it should be able to create the appropriate domain groups.

Am I missing something? Will I be able to run the SQL Server instance on the same server as the primary domain controller? Would the problem be any different if I was trying it on an actual SBS installation?

Thanks,

Reply to
rmi
Loading thread data ...

Hi Matt, I am getting the same error. It stated in the get started guide the following:

If Microsoft Dynamics POS is installed on more than one computer using Windows Vista® or Windows Server® 2008, the LocalAccountTokenFilterPolicy must be turned off.

Needs registry update as per this article however tried with no success:

formatting link
We need to get some help from Microsoft as this is all fairly new...

If you have a solution please share it.

Thanks

Reply to
Eli Abitbol

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.