This is unacceptable both how you have to do a hack job whether or not you are using MCS or PVS.
Let’s take MCS for example first: http://support.citrix.com/article/CTX128580
Here’s my comment to Citrix about their so called workaround:
Quick Deploy creates a shared desktop environment by default and Citrix advertises creating a thousand desktops in 10 minutes. But without KMS, you’r SOL… guess what, you guys jumped the gun again and released an immature almost-working product… again. Let the solution providers do the “workaround” in the mean time. Do you know how this looks when you are training a customer on this and handing the product over to them? A hack job… that’s what. And don’t get me started with the “supported” KMS activation method for PVS. That’s still a hack job. If you have Office 2010, the standard wizard will not render it’s activation successful. You will still have to “hack” into the vDisk and rearm windows and office and shut it down. Oh wait! Almost forgot, make sure you set the KMS to “none” when you are imaging a machine with Office 2010 on it and only set it to KMS mode after you have re-armed it and shut it down. Oh wait! There is one more thing… don’t forget to click “OK” after you set KMS mode on the vDisk but wait, I’m not done, BEFORE you set the disk to standard mode, otherwise it’s not going to work… so basically you will need to open the vDisk properties twice – once to set the KMS, close out and then set the Standard disk mode. The only reason I’m listing these out is for you to hopefully wake up and see how convoluted/confusing this can be to the customer! I’m frustrated, these new products just feels incomplete and immature if you have to hack all the time to make it work. I love how much performance and scalability is renders later and part of the reason I love Citrix but come on guys, I KNOW you can do better than that!
This is unacceptable both how you have to do a hack job whether or not you are using MCS or PVS.
ReplyDeleteLet’s take MCS for example first: http://support.citrix.com/article/CTX128580
Here’s my comment to Citrix about their so called workaround:
Quick Deploy creates a shared desktop environment by default and Citrix advertises creating a thousand desktops in 10 minutes. But without KMS, you’r SOL… guess what, you guys jumped the gun again and released an immature almost-working product… again. Let the solution providers do the “workaround” in the mean time. Do you know how this looks when you are training a customer on this and handing the product over to them? A hack job… that’s what.
And don’t get me started with the “supported” KMS activation method for PVS. That’s still a hack job. If you have Office 2010, the standard wizard will not render it’s activation successful. You will still have to “hack” into the vDisk and rearm windows and office and shut it down. Oh wait! Almost forgot, make sure you set the KMS to “none” when you are imaging a machine with Office 2010 on it and only set it to KMS mode after you have re-armed it and shut it down. Oh wait! There is one more thing… don’t forget to click “OK” after you set KMS mode on the vDisk but wait, I’m not done, BEFORE you set the disk to standard mode, otherwise it’s not going to work… so basically you will need to open the vDisk properties twice – once to set the KMS, close out and then set the Standard disk mode. The only reason I’m listing these out is for you to hopefully wake up and see how convoluted/confusing this can be to the customer!
I’m frustrated, these new products just feels incomplete and immature if you have to hack all the time to make it work. I love how much performance and scalability is renders later and part of the reason I love Citrix but come on guys, I KNOW you can do better than that!