Video Screencast Help

Can we please have a uninstaller for Windows Service Workflows?

Created: 05 Dec 2013 | 5 comments
QuietLeni's picture
0 Agree
0 Disagree
0 0 Votes
Login to vote

Dear Symantec,

I have been creating Windows Service Workflows in SMP 7.1 and the installation process was to generate an installer, then run the installer and then run the install.bat in the \bin directory which essentially includes:

InstallUtil.exe -i MonitoringAgentService.exe
sc config "Workflow Windows Service" depend= "SWFSVR" obj= "NT AUTHORITY\NETWORK SERVICE" password= ""
net start "Workflow Windows Service"

When removing, it was quite simple as the installer placed an entry in the Add & Remove Programs Control Panel, so all I needed to do was to run the Uninstaller in there and all was well.

Now that WF 7.5 is fully released, there is no installer for Windows Service Workflows and you just generate the directory and just run the install.bat in the \bin directory (which seems not to have changed). All is good... ...until you want to uninstall the workflow. There is no uninstaller and the "InstallUtil.exe" does not  include an overt argument in the command line. I have trying -r and -d, etc, but to no avail.

I do not really know what the InstallUtil.exe does, so I am loath to just run a:

sc delete "Workflow Windows Service"

and then delete the folder, as I do not know what else the InstallUtil.exe does!

So, can we please have a corresponding uninstaller or a parameter for the InstallUtil.exe?

Kindest regards,

QuietLeni

Comments 5 CommentsJump to latest comment

reecardo's picture

Typically when I want to kill a workflow windows service, I run an "sc delete <blah>". One thing this doesn't do is go out and remove the now useless VD in IIS (if one even exists in IIS - I'll have to double check that), as well as any deployed code (also useless at that point). Without looking at the code, I'm pretty sure that's what it should do.

0
Login to vote
QuietLeni's picture

reecardo,

There was no VD in IIS for this Workflow - it did not need it and I cannot work out why it would need it?

The deployed code is a given, but my questions are still, if the install.bat is using the InstallUtil.exe to "install" the MonitoringAgentService.exe, what else is the InstallUtil.exe doing? I mean, do I need it at all?

What is the point of an Asset Management Solution that needs excessive management? Let me help you.

0
Login to vote
reecardo's picture

WF windows services don't have a VD... I'm pretty sure that they're just invoked by hitting a method in a DLL (or something similar)

+1
Login to vote
TGiles's picture

QuietLeni,

InstallUtil.exe is a Microsoft utility. You can get additional information about the utility from here.

This functionality was apparently disabled due to concerns that IIS virtual directories were being created for Windows Service and Task Tray applications distributed through the use of the installer. If this occurs it causes issues with multiple projects executing under the same ServiceID. 

In my testings I wasn't able to produce this type of result. The projects published with the installer as a Windows service never generated any virtual directories. I've submitted a request to re-enable the publish as an installer functionality for Windows Services and Task Tray applications.

 

+1
Login to vote
QuietLeni's picture

Thnks TGiles. Can we have this installer functionality to work with the new installer style for Windows Services as well?

What is the point of an Asset Management Solution that needs excessive management? Let me help you.

0
Login to vote