App-V: Cisco UCIntegration for Microsoft Lync 8
Here is a really fun one, made ten times worse by Ciscos complete and UTTER lack of interest in helping their customers out AT ALL.
A quick opinion here: STEER CLEAR of Cisco. Their support is notorious for being a joke, if they have an excuse to tell you to take a hike, they will do exactly that. Their software is poorly written, pathetically supported, and just generally not worth much. And no matter how many millions of dollars you just handed them they wont lift a finger to help you with a problem they KNOW the solution to (or imply they do) and would have been easily solvable by any one of the developers in an INCREDIBLY short period of time.
Avoid Cisco at all cost.
Now, on to the show.
This one gets a little hairy in that when you sequence CUCIMOC (the not so short name for the atrociously long "TM" included product mentioned in the header) and try to launch it on a client machine you get an error saying an unhandled exception has occured. Dig through the poorly laid out and nearly useless PRT result log and you find it is because the listening port of 44442 cannot be accessed. The full error is in the report but the net result is...it doesn't work.
In order to solve this problem you need one key thing from the CUCIMOC installer. NewBinary24. This is a binary (and this is poor form because all it seems to do is run netsh, this just seems to obfuscate the exact tasks) that uses netsh to reserve ports and quite possibly register listening ports for the CUCIMOC plugin. Without these being setup (and the sequencer fails to capture them) you will get the, as intended by MS, error that it doesn't have rights.
In my case I used Wise Package Studio 7, clicked on Setup Editor at the bottom of the Windows Installer Editor (after loading the MSI of course), clicked Tables, then on the Binary table, found NewBinary24, double clicked on the data field (sometimes takes three clicks) and wrote the contents out to c:\cisco.dll
On the target machine you then copy the cisco.dll to wherever, in this case c:\ and open an elevated command prompt (this can all obviously be automated by either a WiseScript or MSI and deployed via the task sequence or SCCM deliverable) and type the following:
RunDLL32 c:\cisco.dll, _netshOperations@4
This will call the DLL with the "_netshOperations@4" entry point and perform the functions from the install that were not captured, as the name implies this just runs netsh commands, it's hard to tell how many but there are at least 6 (which is why simply trying to reserve the 44442 port and setup the listener on 0.0.0.0:44442 didn't solve the problem, even though doing so didn't cause the PRT to move on to the next error, which leads me to believe the specific netsh command is not the obvious).
I've verified on a VM three times now that before running this DLL I get an error, and after, it works. This is a TREMENDOUS boon as if you intend to use this software with MOC 2007 then you know that MOC2007 has poorly thought out two-way communication with Outlook, which means you need to sequence the two together, well if you need the UC plugin for cisco you are stuck either taking ALL of office out of App-V, breaking the MOC integration (which is a bigger inconvenience than the ones added by UC) or ditching the UC plugin altogether.
Hope this helps!
Oh also there is a cert in the installer too that if you've gone this far you should be able to find (you can get it and the cdpinstaller.exe in the common files\cisco systems subfolder. I haven't determined yet if it is needed but...if so, it's in there, and the command line is in the MSI. Might as well post it I guess.
certmgr.exe -add -all "CDPCert.cer" -s -r localMachine trustedpublisher
I would include some of these files but who the heck knows how annoyed that might make cisco. If you have specific problems you can post below and I'll do my best to get you through.
App-V: WebEx Productivity Tools Outlook Integration.
The app itself is pretty simple and straightforward, however the way they add the plugin (you have to launch the WebEx Settings app and login to a webex site, and THEN it adds the plugin) is goofy and I could not get the sequencer to pick it up to save my life. The solution is fairly simple.
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\WebExOI.Addin]"CommandLineSafe"=dword:00000000"Description"="ATLCOM Outlook Addin""FriendlyName"="WebEx Productivity Tools""LoadBehavior"=dword:00000003
App-V: Cisco IronPort Outlook Plug-In.
If you are using Office 2010 on Win7x64 you've pobably already seen the joys of getting it sequenced correctly. Well the headaches extend down the line. And poorly written plugins are the biggest issue I've seen so far.
In this case it is the Cisco IronPort plugin for Outlook that allows users to flag messages as spam or not in conjunction with the Cisco spam filter backend.
Nearest I can tell the problem lies in the fact that if you want FULL functionality from Office 2010 you have to use the 32-bit version, the ADK doesn't have full support for the 64-bit version. And due to...it being microsoft I guess...the only way to get it working is to sequence on Win7x86. Well when you go to sequence the IronPort plugin it does NOT translate over well AT ALL. Which is fair enough, there is a reason why they suggest sequencing on the same arch/level/os as your target machines. And sequencing it on Win7x64 doesn't work because your copy of office wasn't sequenced like that.
Making matters worse Cisco is AWFUL about error messages and logs. The error message you get when launching Outlook is literally just a message that tells you to contact your admin. The admin is instructed to run the diagnostic tool, which is fine but the registry errors I got in particular look something like this:
Trying to read registry information.
Result OK.
Failed to read registry information: Outlook.Addin.Cisco
Windows.Registry.Location does not exist.
Could they have told you exactly WHAT key they tried to read? Or exactly WHAT key they couldn't find? Of course. Do they? No.
So the fact that EVERYONE using outlook gets this plugin finally convinced me to bump it to the category I am LOATHE to bump things to..."sequenced with office"
Another app with this problem is Communicator 2007. So now my patches for Office, Communicator and IronPort are now all tied to one another...but at least it works...
The alternative it to mail a brick to Cisco and ask them to politely describe what the hell is missing, or the next one doesn't come FedEx. ;p (That's the two day old migraine talking, don't actually mail bricks...it's bad for your carbon footprint.)