WordShark - SCCM deployment not working

[mullet_man]

Hi all,

 

Has anyone managed to deploy WordShark out via SCCM?

 

Just doesn't work for me, getting failure errors mostly 1603.

 

If I run it manually via a batch file it installs fine, but run the same one via SCCM and it fails. I've checked the documentation and I get the feeling as it runs manually this might be a SCCM issue?

 

Anyone ran into similar issues?

 

Am trying to move all my software into SCCM, and although wordshark is only installed on a few devices it would be nice to get everything as automated as possible.

 

Cheers.

 

- - - Updated - - -

 

Just seen @mr_wordshark any help?

[mullet_man]

OK after a lot of swearing, and head scratching I might have found a solution.

 

Looks like the msi command /qn doesn't work when ran with SCCM but if I use /qb it does.

 

It means install box appears but I can live with that, and I can add in /qb!- to remove the cancel box it seems.

 

Will confirm at some point in the next few days and post the full command line incase anyone else needs this in the future.

[mullet_man]

Well am still struggling with this. Thought I was getting somewhere but still not playing it seems.

 

Has anyone managed to successful deploy wordshark?

[mdrabble]

Will the deployment run manually with the /qn

 

I had an issue with some serif where either it didn't deploy with other software or stopped other software deploying.

 

I ended up deploying using a power shell script in my TS which worked without issue.

 

Wondered if you could do the same.

Edited May 6, 2017 by mdrabble

[Blue_Cookeh]

Can you post the batch script you were using?

 

If it's an MSI file by default there's nothing SCCM would do to stop /qn working, that would be down to whoever packaged the MSI breaking it

 

EDIT: I also take it you read this? It looks like you need a little more to get it to silently install: http://www.wordsharksupport.co.uk/docs/si.pdf

[mullet_man]

Hi both,

 

If I run the command line locally from a batch file it installs fine no problems the command line has /qn as you would expect.

 

If I use the same command with sccm it fails. I've tried running the command from a batch or just as you would when importing an msi into sccm.

 

Although I might have a break through, if I run with sccm and choose Only when a user is logged on and allow the user to interact but add to the command /passive it has installed on a test machine today. I'll need to fire up some more on Monday to see if it actual deploys to the actual clients i need workshark installed on.

 

I've read and reread the documentation a lot of times and still struggled. As I've said running the batch file manually works a treat but just fails with sccm.

[mdrabble]

Not sure why my MSI has issues - but this is the workaround I have used, so may work with wordshark.

 

 

• Create a PowerShell file with the same command line details to install your software (don't put any path details) - msiexec /I "software.msi" /q and save in the same location as your msi
  
• Create a package in SCCM
  
• Tick this package has source files and locate software location.
  
• Do not create a package
  
• Distribute Content
   
  
• In your TS add Run PowerShell Script- browse and select your newly created package
  
• In Script Name - enter the filename of your PowerShell script
  
• Change PowerShell execution to Bypass
  

 

Hope that helps.

 

Test your TS and your MSI should have installed.

[mullet_man]

Thanks mdrabble but I think I've cracked it, the MSI will not install if it's set as hidden in SCCM. So after lots of testing I've managed to get it to deploy.

 

Here is what is working for me anyway.

 

 

 

It show's the install progress bar but that's all, and with passive set the user can't cancel.

 

Also I've ran into an issue with the detection method, so I've had to set it based on a file rather than the MSI.

[mr_wordshark]

Thanks very much for this - we have noted this ready for any other techs with SCCM queries.

[DavR]

Hi guys - came here as we've just bought Wordshark, and this solution, and a link to it, is now included in their official release notes!

 

Probably too late for the original posters, but for anyone else who comes this way (and perhaps @mr_wordshark), I've just tracked down the root cause of the SCCM failure on my setup - it's a permissions thing.

 

As part of it's pre-reqs, the MSI installer checks that the 'wordshark-shared' network folder is present and correct. This is fine when running as a user, or under a user context, as the user will have permissions to view this. However, running under the system context in SCCM, you will also need permissions for the computer account to read the wordshark-shared folder. So, just like your deployment share, Domain Computers are going to need read permissions to browse to and read that folder.

 

I put "Domain Computers - Read" on my whole application share and that fixed the problem. Others may want to experiment with browse permissions or whatever else, but I was happy with that.

 

This requirement is mentioned in the troubleshooting notes in the Appendix of the install notes for the current version, but as far as I can see it isn't mentioned in the main install notes.

[mullet_man]

Hi guys - came here as we've just bought Wordshark, and this solution, and a link to it, is now included in their official release notes!

 

Probably too late for the original posters, but for anyone else who comes this way (and perhaps @mr_wordshark), I've just tracked down the root cause of the SCCM failure on my setup - it's a permissions thing.

 

As part of it's pre-reqs, the MSI installer checks that the 'wordshark-shared' network folder is present and correct. This is fine when running as a user, or under a user context, as the user will have permissions to view this. However, running under the system context in SCCM, you will also need permissions for the computer account to read the wordshark-shared folder. So, just like your deployment share, Domain Computers are going to need read permissions to browse to and read that folder.

 

I put "Domain Computers - Read" on my whole application share and that fixed the problem. Others may want to experiment with browse permissions or whatever else, but I was happy with that.

 

This requirement is mentioned in the troubleshooting notes in the Appendix of the install notes for the current version, but as far as I can see it isn't mentioned in the main install notes.

Ah well spotted Dave, I wondered why it would install fine under a user context but then bum out when installing under sccm. This makes totally sense now.

 

Hopefully @mr_wordshark sees this and can make the changes on the install notes.

 

I'll make the change on my SCCM and shared folder at some point this week.

 

Thanks

[Arthur]

As part of it's pre-reqs, the MSI installer checks that the 'wordshark-shared' network folder is present and correct. This is fine when running as a user, or under a user context, as the user will have permissions to view this.

If there's a custom action in the MSI that performs the network check could you simply remove it with an MST? Then you don't have to change any permissions.

[DavR]

If there's a custom action in the MSI that performs the network check could you simply remove it with an MST? Then you don't have to change any permissions.

 

But what if the folder really isn't there? Much calamity will surely ensue!

 

/sarcasm

[mr_wordshark]

Thanks guys,

We have seen this and based on the helpful observations from DaveAshworth and Mullet_Man above we have now modified the network installation instructions. These will be released within the next day or two. SCCM is mentioned in the main install instructions, with a note pointing SCCM users to the detailed SCCM appendix. We are really grateful for this feedback given we don't use SCCM ourselves. Please keep it coming! Sorry, Arthur, we don't have a custom action in the MSI that can readily be tweaked, and I suspect if we had then this could add complication for some techs.

Rik

(Support Manager, Wordshark & Numbershark)

[email protected]

[DavR]

Good community response @mr_wordshark, thanks.

[lordasb]

well my battle with numbershark is still going down, really love that replies here are being added to the installer but, dam its complex. 21 years and this i think is the hardest one yet and that includes some of the exam software with 3 different parts..

 

my issue, server is running and up, make the shared folder and installed following the guides included to make the sccm part which sadly fails.

 

tried to go old school and just install the dam client on a test VM, just says that number shark cant be found at the numbershark-shared$ folder.

 

looks right, but who knows at this time of night.

 

at this point i might just delete it all and start again part from the server licence side of course as thats working.

Edited November 17, 2021 by lordasb

[DavR]

If you look in the properties of the Numbershark shortcut on you client, are the Target and Start in locations what you'd expect?

 

Target should be the Numbershark exe, which is usually locally installed.

 

Start in should be your numbershark-shared folder, which is usually networked.

 

Obviously these will vary depending on what options you've chosen.

[mullet_man]

well my battle with numbershark is still going down, really love that replies here are being added to the installer but, dam its complex. 21 years and this i think is the hardest one yet and that includes some of the exam software with 3 different parts..

 

my issue, server is running and up, make the shared folder and installed following the guides included to make the sccm part which sadly fails.

 

tried to go old school and just install the dam client on a test VM, just says that number shark cant be found at the numbershark-shared$ folder.

[ATTACH=CONFIG]63689[/ATTACH]

 

looks right, but who knows at this time of night.

 

at this point i might just delete it all and start again part from the server licence side of course as thats working.

 

What error are you getting with SCCM?

[lordasb]

hi Mullet_man

nothing just that its errored, starting back with the server side tonight, checking step by step again, even though its running i think its the folder is just wrong from my end.

 

hi daveashworth

i will take a look finished checking the core steps :-)

[lordasb]

can someone post a snip of what their numbershare-shared$ folder looks like please? I shared it in my first post but have tried moving it to the

C:\white space software\White Space Ltd\Numbershark 5 Network

folder as well that does not work either.

 

will try manually installing it to a test VM and seeing what it says.

[clareq]

I have Workshark 4 running from the server - mapped drive to the workstations. The target in the shortcut is P:\Wordshark4\wordshark-programs\Wordshark4nrun.exe, and the start in P:\Wordshark4\wordshark-shared. It's certainly worth a try with v5.

[lordasb]

thanks for the replay @ClaireQ will give that a go from the test client end

[lordasb]

ok got the "agreement" splash screen up :-)

 

so thats something...

[lordasb]

updated, thanks for the hint, didnt help it needs a sound card and headphones connected which Virutal machines never have...

[Oaktech]

updated, thanks for the hint, didnt help it needs a sound card and headphones connected which Virutal machines never have...

 

Can you pass sound through from the client?