RSS 

How To: Deploy Citrix Dazzle Plug-in with Merchandising Server

In this AskSupport How To video you will learn how to Deploy Citrix Dazzle Plug-in with Merchandising Server

Tags: technical support merchandising server dazzle citrix receiver how to
Views: 2,011
Rating: 5

Transcript : Good day, everybody. Thanks for tuning in to Citrix TV. This is Wayne Beaver here from the Worldwide Support Readiness Team. For the next five minutes or so, I’m going to give you a brief walkthrough on deploying Citrix Dazzle Plug-in with our Merchandising Server version 1.1. So, sit back, relax, and enjoy the show. Okay. First off here, we have the Merchandising Server’s Administration Console, and we’re looking at the plug-ins area where we install and upload the plug-ins and make them available for rules and deliveries. So we can see here that we do have a Citrix Dazzle plug-in that has been uploaded to the merchandising server. Now you can do this in a couple of ways. The way I did it, the way that most people would do would be to go to the get new plug-ins. Now here we’re talking to citrix.com to get a list of the plug-ins that are available. We can simply, for instance, select the secure access plug-in, and we can say download to server, which will move all the files—the XML file and the installer file necessary for that plug-in to install--and put it to the server so that it would be available here in uploaded plug-ins. The other way that you can do it is to grab the XML file manually, and the MSI file or XE file installer manually, put them somewhere accessible to browsing here, and we can put them in the data file in the plug-in here and simply press upload, which would have the same effect. Would cause the plug-in to be listed here in the uploaded plug-in section. Once we have the plug-in uploaded to our merchandising server, our next step is to set up a rule or to make sure a rule is available, which will select the users based on certain criteria that should have this plug-in made available to them. And then, secondly, we will select a delivery option, to decide how and when that plug-in is delivered to rules…to users that make the rules match. So let’s jump in, first of all, and have a look at rules that we have set up. In rule management here, we can create, edit, or delete rules that have been created. And here we see a rule called DazzleRC, which I have created to deploy Dazzle. So this is a rule to deliver Dazzle to all. And it’s looking at the domain field and checking whether that domain is the kmsdc01. So this is basically saying this rule will match for any user that logs in to the domain…or logs in from the domain kmsdc01 and contacts the merchandising server through their Citrix Receiver. If they’re from this domain here, then the rule is matched and they will be able to download any deliveries that are set up for that rule. And we have a delivery here, as well. This is the delivery page. Here we have a delivery set up for Dazzle for AD Users. If we have a look at some of the details of that from clicking the (inaudible) button. We can see the things that need to be created when we’re scheduling our deliveries. So, first of all, we give the delivery a name. There’s only one delivery here in our set of deliveries, so the evaluation order will simply be the one rule here, Dazzle for AD Users. So that will be evaluated first. If the user whose receiver is contacting the merchandising server satisfies that rule, which we saw was to belong to the kmsdc01 domain was the only criteria, then this delivery will be available to them. It’s not the default delivery. The default delivery would mean this delivery gets given to everybody. So we have some other options for things like silent install, which I’ll say yes. Which will not present any of the installation dialogs to the user. How often to check for updates of plug-in. And some completion text, which will be shown to the user once the plug-in has been downloaded and installed. And some support details that you can put in there that will also belong to that plug-in. And then we actually choose the plug-ins that we want for this delivery. In this case, the Citrix Dazzle plug-in, which was one of the plug-ins available as an uploaded plug-in from the merchandising server. And the action for this is to simply install. Now the configuration. Each plug-in will have its own unique configurations. In the case of the Dazzle plug-in, remember that Dazzle is kind of a PN agent replacement, so that gives the users the ability to assign their published applications to shortcuts on their desktop. The main thing that we need here, first of all, is the store configuration. So this will be the address, and in the example as shown there of our PN agent site from web interface. That’s how we access the store and data http or https. Is it secured or not secured. Contacting that store. Two other Dazzle options is to allow users to add their own stores with these values here, A meaning always they can. And allow users to save their passwords locally. Again, we have the value of A that we’ve setup. We could say no, put an N in there, and then users would not be able to save their passwords when using this plug-in. The name of the start menu folder. Again, you can override the fol…would say Dazzle Applications. We could override that. And a checkbox to whether or not to use legacy file type association icons. More about those in the Dazzle training themselves, those options there. The rule that this delivery is associated with. So here we’ve picked the rule that we saw, DazzleRC, which was matched against any user logging in from the kmsdc01 domain. And then, finally, we can schedule our delivery either to deliver it now, or deliver it on a particular schedule. Once we have these details in place, the delivery now has been set up, and the delivery will be available to any users whose receiver contacts the merchandising server, who is logged on to kmsdc01 domain. The Dazzle plug-in will be downloaded and installed with those configured parameters. So that’s about it for deploying Dazzle through Citrix Merchandising Server. Thanks for spending the time to have a look at this, and I hope you have no problems now when your deploying your Dazzle plug-ins through Merchandising Server. So this is Wayne signing off, and thanks very much again for your attention. Bye.