Workflow Soluiton

man these instructions suck !

I copied Altiris.ServiceDesk.2009.exe down to my local machine from the server. Ran through the install and then it halted on IIS V5 must be installed. huh ? that is xp - I am running windows 7 64 bit home premium

Ok lets try to install Symantec.Worklow.Solution.2009[1].exe -----when I down load this from the server to my laptop -

I get Symantec Workflow Solution cant be run now from the server.

Navigate to my local laptop - when I click on Syamtec.Workflow.Solution.2009 from my download folder  it says the version is not compatible with the version of Windows I am running.

their has to be a easy way to install the Workflow Designer locally!

frustrated with this product

OK finally found the install article

this worked !

just wish their was a way to easily download the Workflow projects and make sure they are sycned. Have to realy pay attention to versioning

My solution was to download the entire projects folder and deployed folder locally.

https://www-secure.symantec.com/connect/forums/installing-servicedesk-workflow-designer7-windows-xp-or-windows-7

Now that I have everything installed I am getting a license error? I thought using the install from the server would transfer the license?

If this is 7.0, 7.0 SP1, or 7.0 SP2, bring up the Notification Server credentials tool and verify the NS information is accurate.

 it is 7.0 sp2

I brought up the NS server credentials Manager and hit test.

I get test succeeded.

-- man this thing is slow to load locally!--

everything is marked as

You use default URL, Process Manager Integration must be enabled

and

Component is bound to service context [ServiceDesk] but the license provider for this context failed to provide a license.

The Component is bound to service context [ServiceDesk] but the license provider for this context failed to provide a license
errors all arise from either of the following:

1. having a bad ServiceDesk license

2. Project Service ID (in project properties) got regenerated and doesn't begin with a ServiceDesk context like INCIDENT- or CHANGE-. This can be fixed by reopening the package, and ensuring generate new Service ID id NOT checked.

These errors specifically apply to ServiceDesk components only however.

The You use default URL, Process Manager Integration must be enabled
arises from not having anf PM information populated for the server that you've set as default in your Local Machine Info. Right click on the "little green guy" in the task tray, ID which server is set as Default Server, then verify information for that server is populated.