Common Provisioning Server 5.0 Issues

7 04 2009

As the old saying goes…it’s easy to make something complicated and very hard to keep it simple.  The same holds true with Citrix Provisioning Server.  While the 5.0 version has added a lot of much needed and requested functionality it comes at the price of complexity.  Don’t get me wrong…it’s still a great product but with any major revision there will come a learning curve on the development side.  Listed below are some quick notes regarding issues I have encountered during recent implementation engagements with PVS 5.0 SP2.

  • Accounts that are a member of a security or distribution group with a “/” in the group name will fail to authenticate successfully to the Provisioning Server console.  Even if the group in question is not used to control access to the PVS console, simply being a member of a group with the aforementioned special character will break authentication for the user as indicated by the following message:

  • When trying to access the PVS server from a remote system such as a workstation with the console installed locally the logon fails and produces a message stating that an error occurred communicating with the server as noted below.  There are a few possible causes for this error.  When specifying the Provisioning Server to connect to be sure to use the IP address for the PVS server instead of the hostname.  I have seen in several environments that a remote instance of the console, i.e. not the instance local to the PVS server, will not connect using the hostname.  Another possible cause can be a firewall enabled on either the machine on which the PVS console is installed or the PVS server itself. 

pvs_error2

            

 

 

 

               

 

 

 

As stated this is intended to be a very brief overview of issues fresh in my head but please feel free to post additional suggestions or encounters.

Advertisements

Actions

Information

5 responses

9 04 2009
Pete Downing

Matt,

Feel free to drop me line because I would to discuss these “issues” you are having with PVS 5.0 and in-fact tell you how we improved them!

Pete Downing
Senior Product Manager, Provisioning services
Citrix Systems, Inc.

1 06 2010
Jann

Pete,

I have noticed your posting on several sites. I am having issues with the citrix provisioning server console and was wondering if you could help! When I try and connect I get the following errors:

local host – MMC detected an error in the snap-in and will unload it. Once I click ok this is the error that follows fx:{d4362548-2b4a-4f95-91b1-4f813d7b18e7}

I have changed the console.exe file log to debug and to error looking for a different result and depending on how I try and connect I get a different result. Ip will give one result where as the server name will give another. Also I have un-installed and reinstalled the console thinking that might work. Deleting the provisioning server file doesn’t work. Any help you could give would be greatly appreciated.

2010-06-01 18:44:10,306 [8] ERROR EnterpriseAccess.MapiChannel – EndpointNotFoundException: No DNS entries exist for host vdspvs01.niprnet.mil.

2010-06-01 18:44:10,322 [3] ERROR EnterpriseAccess.MapiChannel – CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

2010-06-01 18:44:10,322 [3] ERROR EnterpriseAccess.HandlerBase – GeneralCommunicationExceptionHandler

2010-06-01 18:44:10,322 [3] ERROR EnterpriseAccess.HandlerBase – return code: 4000

2010-06-01 18:44:10,322 [3] ERROR EnterpriseAccess.HandlerBase – exception type: GeneralCommunicationException

2010-06-01 18:44:10,322 [3] ERROR EnterpriseAccess.HandlerBase – message: CommunicationObjectFaultedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

2010-06-01 18:45:51,401 [3] FATAL EnterpriseAccess.HandlerBase – SetupErrorHandler

2010-06-01 18:45:51,401 [3] FATAL EnterpriseAccess.HandlerBase – return code: 15

2010-06-01 18:45:51,401 [3] FATAL EnterpriseAccess.HandlerBase – exception type: SetupError

2010-06-01 18:45:51,401 [3] FATAL EnterpriseAccess.HandlerBase – message: The system setup is not correct.

2010-06-01 18:45:51,401 [3] FATAL EnterpriseAccess.HandlerBase – source: Mapi

12 05 2009
Michael Friesen

This helped a lot! We were banging our heads against a wall trying to figure out why the console worked for one person on our team, but not the others!

13 05 2009
matthensley

Thanks for the feedback Michael. What was your specific issue? Did you have users who were members of a group with a “/” in the name?

18 11 2009
Jeff Grigsby

I have been working with a PVS deployment since we were running Ardence 4. The product was at first good for us, but had a few issues with performance HA and the occasional missing configuration. Since it became a Citrix product we have had a SR open with Citrix. It has been disastrous and I have put in many hundreds of hours of overtime trying to work it out. We recently upgraded to 5.1 SP1 and more issues have arisen. If I could have switched this out I would have by now. I purchased Zero Clients from Wyse and if they had been thin clients I would have moved on to a VDI deployment by now instead of streaming from the data center out to the desktop. I am sure this product must work somewhere but it certainly is failing for us.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: