/build/static/layout/Breadcrumb_cap_w.png

Skype for Business 2016 Removal

Hi,

I'm trying to remove Skype for Business 2016 from the system through SCCM Task Sequence but to remove Skye I need to add PRODUCT ID.
I search the whole registry but I couldn't find the Product ID.

could yo please help me out how can i Find the product id for Skype for Business 2016. Or which the best way to remove Skype form Client system silently.

ThanksĀ 


1 Comment   [ + ] Show comment

Answers (2)

Posted by: anonymous_9363 7 years ago
Red Belt
0

Like the rest of Office, the Product ID for SfB will be in the XML configuration file you used to install it.

Your quickest option is to search for the word "Skype" in all the XML files beneath the 'root' folder which contains the original set-up executable.

Posted by: JoshRoss 7 years ago
Senior White Belt
0
If you are referring to the Skype that is installed directly with Windows 10, product ID for 2016 version should be this: "SkypeforBusinessEntryRetail" or this "SkypeforBusinessRetail" (remove quotes). You can also google for XML file to get the correct ID or check Microsoft's official page for the list of ID's.

Comments:
  • Hi Josh,

    I tried with that but it won't remove from system
    and this one is installed through Windows Installer setup not through Click to Run setup - niravshah 7 years ago
    • In theory, you could try disabling the skype for business registry, killing all of the processes and not allowing it to launch again. That is as effective as removing it. - JoshRoss 7 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ