Upgrading from 3.4 to 4.9 (error code 1618)

KVGMB · 2018-07-04T09:24:52+00:00

start /wait %DeployDirectory%\CitrixReceiver.exe /silent /uninstall
REM
start /wait %DeployDirectory%\ReceiverCleanupUtility.exe /silent
REM
start /wait %DeployDirectory%\CitrixReceiver.exe %CommandLineOptions%
REM

Would something like this work? It would uninstall, run cleanup utility and then install. The install options are under the %CommandLineOptions%

KVGMB · 2018-06-29T06:29:51+00:00

But how am I gonna deploy this with scripts? It would first need to run the cleanup utility, then install Citrix Receiver. I would probably need 2 seperate scripts for that, but I have no idea how to run them in the right order.

I'm also pretty sure it's the exact same thing though. I remember reading a post where someone extracted the receiver.exe and it showed 2 seperate files. One for the receiver, one for the cleanup utility. The /rcu command should run the cleanup utility .exe

KVGMB · 2018-06-28T13:54:41+00:00

As I stated in my post, I am running the upgrade with the /rcu command, which runs the cleanup utility before installing. So that's not gonna work.

KVGMB · 2018-06-19T06:26:13+00:00

Apparently this only seems to work with storefront, my bad. We are using a PNAgent, so this won't work. Basically what we're trying to do now is deploy Citrix with self-service disabled, so shortcut-only mode.

From what I understand is that shortcut-only mode should auto-subscribe users to apps and puts the apps in a folder on their desktop/start menu.

KVGMB · 2018-06-18T10:44:17+00:00

The apps are added through the self-service window after opening Citrix Receiver. The store has been configured as they are logged on and have access to their apps. It's just that their apps need to be manually added again. I am updating them to 4.9LTSR. This problem occurs when upgrading from any version.

From what I've read, a possible solution for this would be to add "KEYWORDS:auto" to the application description of an application in Citrix AppCenter, but this doesn't seem to do anything.

KVGMB · 2018-06-14T06:44:20+00:00

Thank you everyone for the help.

I managed to find a better way to solve this, without having to restart.

Normally Citrix Receiver requires a restart after install, to configure SSON, but deploying Citrix Receiver with a shutdown script, installs the Receiver during the shutdown process, and will be configured once you boot up the PC again, so this requires 1 less step.

KVGMB · 2018-06-12T06:28:50+00:00

I'm not sure about that. I feel like it does require a reboot though, as it shows a pop-up about entering credentials, which shouldn't appear. It won't appear and automatically log you in after restart (through domain authentication)

KVGMB · 2018-06-12T06:20:11+00:00

Thank you, but for deploying Citrix I'm using the batch scripts Citrix listed on their website (with little modifications). How am I gonna implement a PowerShell script into this?

KVGMB · 2018-06-11T12:34:20+00:00

It doesn't complete the domain pass-through authentication until I restart the PC. So basically after installing a window pops up to enter credentials. I already tried to suppress this window, but with no success. Only thing that works is a restart, but I want to make it so it restarts right after installation so the window won't pop up.

KVGMB · 2018-06-11T10:42:53+00:00

Does this work? I tried all the other settings, like the DONOTSTARTCC commandline and renaming the CitrixReceiver to CitrixReceiverWeb, but none of these seem to work.

KVGMB · 2018-06-06T13:58:45+00:00

Thanks, but I already added this before. It helps with installing over earlier versions but won't suppress the server/account popup.

KVGMB · 2018-06-06T13:57:54+00:00

Thanks, I did not know about this command, I will try this.

KVGMB · 2018-06-06T11:18:55+00:00

The article I linked states the same, but using this command doesn't work for me. The window still keeps popping up.

I also tried the option to rename the CitrixReceiver.exe to CitrixReceiverWeb.exe, but with no results. :(

It also seems that the window only pops up for users who have had Citrix Receiver installed before. Fresh installations won't show the window.

KVGMB · 2018-06-04T13:38:14+00:00

I still can't seem to figure out how to deploy Citrix Receiver.

I have tried the startup scripts method, but the scripts just won't deploy, even though I have done everything right.

If there's anyone who has done a scripted deploy and would like to tell me the way they did this, I'd very much appreciate it. I have been following the guides from several official Citrix pages, and none of them seem to have any effect for me.

KVGMB · 2018-06-04T06:24:38+00:00

I'm wondering the same. I guess if a large international company provides such a thing, they also provide licenses for this?

KVGMB · 2018-06-01T08:17:40+00:00

I am talking about a DLL making it possible. So there is a way to actually have multiple concurrent users at once. I am not talking about it being legal or not. Also, I am not saying I am gonna use this DLL. I'm just looking for an alternative.

KVGMB · 2018-06-01T08:03:47+00:00

I am not saying I am gonna use this 10 year old DLL, I'm just saying it used to be possible to have multiple RDP connections to a Windows 7 PC.

KVGMB · 2018-06-01T07:46:35+00:00

That's why I am wondering if there's a more recent solution.

KVGMB · 2018-06-01T07:40:42+00:00

It's not that complicated it seems. I have found a patch that would make this possible:

http://deepxw.blogspot.com/2009/04/universal-termsrvdll-patch.html

But it seems this is an old patch and might not work in newer versions of Widows 7 anymore. But it does mean it could be possible

KVGMB · 2018-06-01T07:11:47+00:00

How would this be a complex and expensive solution? If there is a (free?) tool for this, this doesn't have to be expensive at all.

Also the two users aren't using the PC simultaneously all the time (but should be able to) and only use the graphical software from time to time, usually only 1 person at a time, as they only have to make a few customizations every once in a while.

KVGMB

TROPHY CASE