powershell | find office 2013 installed features
hi all, i have a client that is having issues with skype for business. this is due to office 2013 being present with lync installed as a feature via add/remove features.because lync office 2013 is installed and skype for business 2016 is installed, users are not able to sign into skype for business which is what they are using in their environment.when you query for lync being installed in this instance, it shows up like so i've tested removing lync via this script - function uninstall-msibyname { 
 
 param ([string]$applicationname, 
 [string]$switches) 
 
 #declare local variables 
 set-variable -name errcode -scope local -force 
 set-variable -name executable -scope local -force 
 set-variable -name key -scope local -force 
 set-variable -name keyname -scope local -force 
 set-variable -name parameters -scope local -force 
 set-variable -name searchname -scope local -force 
 set-variable -name tempkey -scope local -force 
 set-variable -name uninstall -scope local -force 
 
 $uninstall = get-childitem hklm:\software\microsoft\windows\currentversion\uninstall -recurse -ea silentlycontinue 
 $uninstall += get-childitem hklm:\software\wow6432node\microsoft\windows\currentversion\uninstall -recurse -ea silentlycontinue 
 $searchname = "*" + $applicationname + "*" 
 $executable = $env:windir + "\system32\msiexec.exe" 
 foreach ($key in $uninstall) { 
 $tempkey = $key.name -split "\\" 
 if ($tempkey[002] -eq "microsoft") { 
 $key = "hklm:\software\microsoft\windows\currentversion\uninstall\" + $key.pschildname 
 } else { 
 $key = "hklm:\software\wow6432node\microsoft\windows\currentversion\uninstall\" + $key.pschildname 
 } 
 if ((test-path $key) -eq $true) { 
 $keyname = get-itemproperty -path $key 
 if ($keyname.displayname -like $searchname) { 
 $tempkey = $keyname.uninstallstring -split " " 
 if ($tempkey[0] -eq "msiexec.exe") { 
 write-host "uninstall"$keyname.displayname"....." -nonewline 
 $parameters = "/x " + $keyname.pschildname + [char]32 + $switches 
 $errcode = (start-process -filepath $executable -argumentlist $parameters -wait -passthru).exitcode 
 if (($errcode -eq 0) -or ($errcode -eq 3010) -or ($errcode -eq 1605)) { 
 write-host "success" -foregroundcolor yellow 
 } else { 
 write-host "failed with error code "$errcode -foregroundcolor red 
 } 
 } 
 } 
 } 
 } 
 
 #cleanup local variables 
 remove-variable -name errcode -scope local -force 
 remove-variable -name executable -scope local -force 
 remove-variable -name key -scope local -force 
 remove-variable -name keyname -scope local -force 
 remove-variable -name parameters -scope local -force 
 remove-variable -name searchname -scope local -force 
 remove-variable -name tempkey -scope local -force 
 remove-variable -name uninstall -scope local -force 
 
 } 
 
 uninstall-msibyname -applicationname "microsoft lync" -switches "/qb- /norestart" and it works, but when you try to check features in control panel, it errors out with this message - on the positive side, it removes lync, but it breaks office 2013.any suggestions as to a different approach?
if lync was installed with office, you can use the office customization tool (oct) to remove lync.  in effect, it is like uninstalling office and re-installing office without lync/skype.edit:  

https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-customization-tool-for-click-to...
i seem to have fixed this by myself. i disabled probe on my .vcl and this seemed to fix the 503 issues. here is my .vcl for varnish incase anyone needs it(this might work for you)! :slight\_smile:

vcl 4.0;

backend default {

.host = "127.0.0.1";

.port = "81";

.connect\_timeout = 5s;

.… The file is spyware releated ,download the spyware programs at the bottom of my post and update them and run them ,do not remove anything with hijsckthis ,copy and paste the log in here , You were unfortunately fooled by the marketing. The actual updated Lightroom is called Lightroom Classic. It is exactly like you remember with a develop panel, ability to print, etc and will behave and work like the Lightroom you are used to. What you likely installed is a port of the mobile operating system version of Lightroom to desktop operating systems. Adobe calls this Lightroom Desktop which is extremely confusing. What you want to do is to call adobe and transfer your subscription to Lig... Magda, have you found what you need, yet?


I did this many years ago. It is simple… the 2nd time you do it!  

Exit points are simply “interrupts” that IBM supplies. You can attach programs to them, and the programs will automatically run at that point. For setting your AS/400 up to accept FTP logons, for example, the exit point is:  

QIBM\_QTMF\_SVR\_LOGON and the format you wil use is: TCPL0100.


A program inserted there can control WHO can log on, and when.  

To control WHAT they can do, you use another exit point, QIBM\_QTMF\_SERVER\_REQ and use format VLRQ0100.


My notes (from 1999) say I used the IBM TCP manual to get this info, specifically: TCP/IP manual SC41-5420-01 page I-14.


I do not know if it will allow me to post code here, it is long and complex due to the number of variables and some of them being in hex.


Write me (drow@waxie.com) if you would like me to email you my program code.


David Row  

WAXIE Sanitary Supply  

San Diego, CA





This is a link for [Add-ons for Firefox](https://addons.mozilla.org/en-US/firefox/). These are programs written by users or developers that the browser knows how and when to call. The developers of Firefox designed it to allow external programs to be hooked in by users of the browser.


IBM did something similar for a lot of the TCP/IP and other server functions. (And a lot of other things.) When you connect to the FTP server for example, the server checks to see if a program has been registered to process FTP logon requests. The registered program is an ‘exit program’.


Browser add-ons get an entry added to a file someplace within the browser directory structure. In your iSeries, the entry would be added to the Registration Facility. (Not always, but that’s the commonly recognized object for exit points and programs.) Use WRKREGINF to review your registration facility.


To create an exit program, you need to know the parameter list that will be passed to your program and the exit protocol. To find the parameter list, you should start looking at the documentation for the server the exit program will be associated with. The protocol, the meanings of the parms and what to with them, is also there.


A FTP exit program would be structured after documentation within the [File Transfer Protocol exit programs](http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaiq/rzaiqreferenceexit.htm) topic of the Information Center for your release.


Once registered, a server logon exit program (for example) would be called just before the server decides whether or not to accept the logon. Your exit program directly influences that decision by returning an ‘accept or reject’ parameter. It chooses based on examination of the input parms.


The exit program may control who can and cannot logon, where they may logon from, what times of day logons are accepted, or it might accept all logons — its purpose can be simply to write all logons to a log file or to send a message when particular logons happen. Your exit program can do whatever it is programmed to do at that point in the logon process.


It doesn’t have to be a ‘security’ function. It’s whatever you want it to be.


For the FTP server, there are two general exit points. One is just before a logon is accepted. The other is just before each transaction in a session is processed. You can control individual transactions just as you can logons. (FTP client has its own exit points.)


Most other exit programs work on similar principles.


A few issues complicate things.


* An exit program needs enough authority to do whatever it needs to do; it can’t always rely on the authority of the session user.
* An exit program shouldn’t unduly delay transactions; there’s no way to know how often an exit program may be called, so you don’t want it slowing down every single transaction.
* Exit programs may be called by many instances of a server at the same time; it shouldn’t be locking things that are needed by a different instance.
* IBM changes the interfaces at times and the servers themselves can get PTFs; regular, on-going maintenance can be needed — keep the programs direct with little complication.
* There are other issues, but those are enough to consider.


Code a very simple exit program that accepts the parms and returns an ‘Accept’ indication. Don’t have it do anything except maybe send a message to a message queue. That lets you see how the registration facility works and how the parms work. It also gives you a program that you can register and deregister in the future to check whether or not the server is stilling calling your program correctly. (Problems can happen.)


Tom hello [@yash](/u/yash),

maybe i got it. when you said you yesterday installed vertica extension you probably installed knime vertica driver extension.

[verticadriver]

also do you maybe have multiple knime instances on your machine? that would explain why you can’t find workflow from yesterday and why is driver option grayed out (cause extension is not installed).

br,

ivan Did you had ACS common installed in your AEM.

<https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html>




[View solution in original post](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116) hi [@staffan](/u/staffan) ,

sorry for not responding to this sooner.

i know that chromeos now has some support for linux applications. odrive has a linux version, but this isn’t something we’ve tested on chromeos yet.

[agent/cli (linux, macos, win)](https://docs.odrive.com/docs/odrive-sync-agent)

sync agent and cli overview the odrive sync agent provides advanced users with a flexible, scriptable interface to odrive’s progressive sync engine. use it to bring cloud access and sync to almost any environment. the odrive sync agent can be used... There is an MS DOS tool you can use to add a service. It is SC.EXE. I shall illustrate its use with an example.

Suppose, that I had installed two Coldfusion 11 instances named *testInstance1* and *myNewCFInstance*. Their installation directories are, respectively

C:\ColdFusion11\testInstance1\

C:\ColdFusion11\myNewCFInstance\

To add them as Windows services, you could proceed as follows.

Click on the Windows Start symbol.

When you type *cmd* in the search field, a link to the DOS command prompt should appear.

Right-click on the link and select to *Run as Administrator*. You should now get the DOS command prompt.

You can now run the DOS command, SC, to add a Windows service. You will have to do this for each and every instance you wish to add, one instance at a time.

**testInstance1**

Type the following after the prompt and press enter:

*sc create "ColdFusion 11 testInstance1" binPath= C:\ColdFusion11\testInstance1\bin\coldfusionsvc.exe start= auto DisplayName= "ColdFusion 11 testInstance1"*

Explanation:

* You must leave a single space after each equal (=) sign.
* "ColdFusion 11 testInstance1" is the name of the Windows service.
* The start type is Automatic.

![](/legacyfs/online/1191406_pastedImage_20.png)

You should get the result "SUCCESS".

To add the description, you have to run SC once again:

*sc description "ColdFusion 11 testInstance1" "My first ColdFusion 11 instance"*

Explanation:

* You must use the exact Windows service name. It is, in this case,  "ColdFusion 11 testInstance1".
* You may use any description you like. But I would advise you to use something like "ColdFusion 11 instance name\_of\_instance"

![](/legacyfs/online/1191405_pastedImage_16.png)

**myNewCFInstance**

For my second instance, the DOS commands I used to create the Windows service and to add the description were, respectively,

*sc create "ColdFusion 11 myNewCFInstance" binPath= C:\ColdFusion11\myNewCFInstance\bin\coldfusionsvc.exe start= auto DisplayName= "ColdFusion 11 myNewCFInstance"*

Followed by

*sc description "ColdFusion 11 myNewCFInstance" "ColdFusion 11 instance myNewCFInstance"*

Some references:

<https://coldfusionsolution.wordpress.com/2014/11/12/how-to-create-service-for-coldfusion/>

[http://stackoverflow.com/questions/29702700/sc-exe-how-to-set-up-the-description-for-the-windows-ser...](http://stackoverflow.com/questions/29702700/sc-exe-how-to-set-up-the-description-for-the-windows-service)

<https://forums.adobe.com/thread/1152396> 

Should you make a mistake, and wish to delete a service, then see

[How to Delete a Windows Service in Windows 7, 8, 10, Vista, or XP](https://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/ "https://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/") Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V If you're comfortable mucking with the registry, the easiest thing to do is to modify:


* HKLM\SOFTWARE\Khronos\OpenCL\Vendors (for 64-bit applications)


or


* HKLM\SOFTWARE\Wow6432Node\Khronos\OpenCL\Vendors (for 32-bit applications)


These registry keys should contain one REG\_DWORD value for each OpenCL platform.  If you change the REG\_DWORD value for a platform from 0 to 1 then that platform will no longer enumerate.  The nice thing about this method is that if you change your mind, you can re-enable the platform by simply changing the value from 1 back to 0.


The ICD loader extension spec has more detail, if you're curious:


<https://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt>




[View solution in original post](/t5/OpenCL/Uninstall-Intel-OpenCL-Platform/m-p/1109711#M5258)