opensofts.org

Home > View Composer > View Composer Agent Initialization State Error 17

View Composer Agent Initialization State Error 17

Contents

Enter the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\vmware-viewcomposer-ga and match the settings as per the screenshot below. Show 10 replies 1. Environment Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2 Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3 Domain Services for Windows Vmware ViewConnection Server 4.5 You can not post a blank message. have a peek at this web-site

Problem was on my KMS server. Like Show 0 Likes (0) Actions 3. viewcompservprob.JPG 97.2 K Like Show 0 Likes (0) Actions 8. I did not find the key but went ahead and created it. https://kb.vmware.com/kb/1026556

View Composer Agent Initialization State Error (16) Failed To Activate License

Like Show 0 Likes (0) Actions Go to original post Actions Remove from profile Feature on your profile More Like This Retrieving data ... If the KMS is found, the Vista machine will request a six-month activation. I bought licenses for View with composer.My environment are:2 x vCenter server 4.0.0 build 258672 (windows 2008 r2 + composer 2.5.0-291081)4 x ESX 4 u2 (2xESX per vCenter server)2 x View Then OK your way out of the GPMC.

Incapsula incident ID: 277000430067085154-97277538938978993 My VMware | VMware.comSearch ActivityBrowseAll ContentBlog PostsDiscussionsDocumentsPollsBookmarksPopular tagsCommunitiesGroupsPeopleLog inRegisterHomeVMTN Forums Mobile AppsBlogsTwitterFacebookGoogle+LinkedInYouTubeGroupsPodcasts vSphere NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware This error will occur during the quick prep phase as quick prep and VMware View only support KMS and not MAK activations. Incapsula incident ID: 277000430067085154-365650915481682618 VMware - Get Involved About me Podcasts View 6 Upgrading to Citrix Storefront 2.5 Centralizing an Endpoint with VMware Horizon Mirage How to fix VMware View View Composer Agent Initialization State Error (6) Related Tagged with: vmware If you enjoyed this article, please consider sharing it!

Please type your message and try again. 10 Replies Latest reply: Apr 12, 2012 9:04 AM by joshuatownsend View Composer agent initialization state error (16): Failed to activate the software license Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) cfeskens Oct 4, 2010 11:31 AM (in response to LarryBlanco2) What was the KMS Incapsula incident ID: 277000430067085154-68934856479146676 Request unsuccessful. Continued vhorizon Pages About mePodcastsView 6VMware - Get Involved The Latest Droplet Computing I’ve seen a little bit of the future recently and its platform[…] More Thanks for dropping by!

Then navigate to "Computer Configuration\Preferences\Windows Settings\Registry"  right click and select "New\Registry Item". View Composer Agent Initialization State Error (18) Failed To Join The Domain Author: Dale Scriven Like this:Like Loading... Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) iforbes Oct 3, 2011 9:11 AM (in response to Linjo) Where can I find Windows 7 virtual desktops have problem find KMS server.

Provisioning Error Occurred For Machine View Composer Agent Initialization Failed

Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) maros141 Oct 4, 2010 2:22 PM (in response to cfeskens) It was mistake my Like Show 0 Likes (0) Actions 6. View Composer Agent Initialization State Error (16) Failed To Activate License I corrected my KMS server and now linked clones are functional. View Composer Agent Initialization State Error (16) Failed To Activate License (waited 1225 Seconds) Incapsula incident ID: 277000430067085154-365651220424360634 Request unsuccessful.

Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Check This Out If the Vista machine is unable to reach the KMS prior to the expiration of the six-month activation, it will enter a 30-day grace period, following which it will enter a With an addition of a registry key you can skip the license check phase within quick prep and the  creation will complete. Adding the key to group policy preferences also works for a pool that has already been created and has received this error which means you don't have to trash the pool View Composer Agent Initialization State Error (9) Failed To Relocate Disposable

Maros Like Show 0 Likes (0) Actions 4. Ideally you would add this registry key to the parent vm before creating the snapshot and pool, however for the forgetful amongst us you can also add the key through group Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS http://opensofts.org/view-composer/view-composer-agent-initialization-state-error-22.php This can pose a problem when running a small demo environment or home lab as you will not be able to complete the quick prep process and pool creation will fail

Bookmark Email Document Printer Friendly Favorite Rating: ERROR: View Composer agent initialization state error (18): Failed to join the domain (waited **** seconds)This document (7007931) is provided subject to the disclaimer Kms Dns Entry Request unsuccessful. He was changing DNS record (service location) for KMS server.

Join 32 other subscribers Email Address Disclaimer This blog and any other post made by me on the internet is representative of my views only, they are not the views of

Popular TagsCitrix VMware Podcasts Set your Twitter account name in your settings to use the TwitterBar Section. View environment is using both vCenter servers + 2 composersThanks composer.jpg 490.6 K event.jpg 429.7 K 20431Views Tags: none (add) composerContent tagged with composer, connectionContent tagged with connection, errorContent tagged with However all is not lost! Windows 7 Kms Key But it seems to be working.

Incapsula incident ID: 277000430067085154-282139086046954169 Request unsuccessful. When I create new desktop pool with Windows 7 32bit, automatic pool, floating, linked clone, quick prep. You must found this DNS record-service location for KMS server and change it to correct server.vlmcs.tcp. on TCP port 1688.-KMS Activation: Background InformationWhen a Vista machine is attached to a network, http://opensofts.org/view-composer/view-composer-agent-initialization-state-error-18.php After two weeks, the Vista machine will automatically try to obtain a new six-month activation from the KMS server.

Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) joshuatownsend Apr 12, 2012 9:04 AM (in response to iforbes) Look here for instructions After few minute is status changed to Error (View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds)Could you please help me, where is problem If not, that is the issue.You'll have 4 options:Option 1: Get KMS licenses in place for Win7 from Microsoft. -by far the easiest.Option 2: Use SYSPREP instead of QuickPrepOption 3: Add DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another.

All that is left to be done is reboot the VM's within the pool and wait a few minutes for the quick prep to complete correctly. We're rolling out KMS for the first time and bumping into this error on provision. Add the key by creating a new GPO (or an existing one if appropriate) on your VMware View desktop OU , you have created a separate OU for your View desktops Or be creative if it's your test env.Option 4: Hack the reg key that supossedly has composer activate.

Seems to be working.Larry Like Show 0 Likes (0) Actions 2. Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) maros141 Sep 27, 2010 4:05 AM (in response to LarryBlanco2) I found problem on Incapsula incident ID: 277000430067085154-282139077457019577 Request unsuccessful. I activated a few desktops individually with KMS licenses, but running into this issue when trying to update pools en masse.

Share This Page Legend Correct Answers - 10 points Request unsuccessful. Below is the info:HKLMsystem/CurrentControlSet/services/vmware-viewcomposer-ga/SkipLicenseActivation to '1'.Of course the Win7 desktop will be in evaluation-mode until the eval-period expires but can be useful in a temporary setup or POC,The above is not At no point in this process does the Vista client machinec communicate with Microsoft regarding activation. Re: View Composer agent initialization state error (16): Failed to activate the software license (waited 1650 seconds) LarryBlanco2 Sep 24, 2010 3:10 PM (in response to maros141) Glad you figured it

One Response to How to fix VMware View Composer agent initialization state error (16) Newsletter: June 7, 2014 | Notes from MWhite says: June 7, 2014 at 10:47 pm […] VMware I must solve a problem with my KMS server and then I will be solve problem with View Composer. The cusually can be found by running the ipconfig program on the Vista machine and looking at the Connection-specificccDNS Suffix. Document ID:7007931Creation Date:17-FEB-11Modified Date:22-OCT-12NovellOpen Enterprise Server Did this document solve your problem?

So long as the KMS server is available, the Vista machine will always remain activated.