Did you have any errors on the install? maybe with the analysis database? is the SQL off-box ?

You may want to try changing the port the process manager is running under and setup AD authenication during the install

I didn't had any errors on install and the analysis database wasn't installed. The SQL is off-box.

Where do you want to change the port? I saw on the settings two areas where I can change this option.

1. Under Server Details the connection port for accessing through the process manager. With actual value 80

2. Under Server Details => Server Extensions => Server Port Number with actual value 11434

Which port do you want to change?

Thanks for answers.

Just curious... can you actually hit the service http://Altiris02/ProcessManager/Userman/Userman.asmx with the admin@logicbase.com/admin login in a browser session? Also, can you verify that your task tray tool is in fact pointing to that Altiris02 box (and not some other box like (local))?

With your changes I couldn't reach the Userman.asmx page. Following the settings I changed:

I also add the Event Viewer error:
-----------------------------------------------------------------------------

Phiestand, where did you install Process Manager? Local or Altiris02? It sounds like you have off-box SQL but you ran the installer locally...

The Process Manager is installed on Altiris02 but the SQL Server is on a different server. Can the process manager only run on the SQL Server?
On the Installation I didn't saw any connection problems between Altiris02 (Workflow Server) and SQL01 (Database Server).

For explanations:

In my test environment I've got 5 Servers

1. DC with DNS / DHCP etc.
2. Altiris01 with Altiris Version 6.x
3. Altiris02 with Workflow Solution
4. Altiris03 with Altiris Version 7.0
5. SQL01 with all Databases

Now I want to run Workflow Solution on Altiris02 with the database installed in SQL01.

Do you see any problems with this configuration?

Thanks for answers.

 I'm currently having problems with getting the Cube reporting to work .. WF7 is running but now we have the reporting to find a solution . i hope that the SD7 documentation will help with this .. Calling support is worthless effort .. I hope they drop a ton of documentation this Friday on the install of SD7

I just had to update the Default App Pool to use my Altiris Service account and then add it to that group. The ASP.NET stuff was not needed.

Hmm... doing this breaks the Software Portal for NS.

I didn't checked the actual configuration with other services, running on other servers. Did you install workflow solution on the same server as SMS ?

Thanks for reply.

After working with Symantec Support and doing my own troubleshooting, DO NOT install it on the same box as NS. As soon as I would get one part working another app would break. I even tried creating a new website and app pool on the NS box just to find out that the Task Server\Client would try to register to this new website even though I had an allias defined and mapped for each site.

Save yourself the headache, put it in a new VM server. Also create a new service account for it. Don't re-use your Altiris service account. The installation will fail if you try to use the same SQL server that NS is using.