Tuesday, January 3, 2017

vRA and SCCM Timeout Issue

virtualpatel.blogspot.com: vRA and SCCM Timeout Issue: Hi, OK here I am again. Been away for few months working on various projects including vRA, vROPS, SRM, VIN, vRB etc.etc. And one of the...

vRA and SCCM Timeout Issue

Hi,

OK here I am again. Been away for few months working on various projects including vRA, vROPS, SRM, VIN, vRB etc.etc. And one of them is MSB. Yes its a new term I've learned and worked on with one of the Federal client along with VMware NSBU. 

But here today I'm going to discuss about the timeout issue with vRA and SCCM deployment.

Now before we begin let me give you the overview of what we are dealing with.

In my recent project Im working with VMware on a vRA Distributed architecture with a little bit of vRB and also integrating the SCCM on which the client is heaving depending on for VM/s deployment. 

Mainly these are windows 2008 R2 Std and Windows 2012 R2 Std VMs. They are leveraging SCCM to do all major tasks such as putting patches, updates, updating AV signatures, putting legacy apps, some monitoring apps such as WhatsupGold and Logrhythm etc. etc.



So once the VM is built in vRA its been handed over to SCCM for further provisioning and there is a default time out setting in vRA which is only 15 minutes.



So as you can see the default setting for SCCM machine registration timeout is 5 minutes. So now
lets assume you are doing few tasks using SCCM e.g. Installing OS, putting patches, doing AV updates, putting legacy or custom applications or softwares etc. etc. then you need time to finish all those tasks in the background on SCCM side. With having 5 minutes timeout vRA wont know what is the status of the SCCM VM as the whole process may not be finished and the gugent might not be updating vRA with any status at all so you may see the process/task in vRA as its still running and not completed and eventually the task will fail as no signal received by vRA in time (which is 5 minutes). So to avoid that you need to increase that time out setting by enough time that you can finish the required tasks on SCCM side before hitting the timeout window of vRA. We had to keep it at 45 minutes (screen shot below) on a safer side which accounts few reboots of the OS along with other tasks listed above.




After doing the above change we were started receiving finished tasks in vRA successfully which were handled by SCCM then gugent updates vRA server with appropriate status.

I will cover the SCCM and vRA in one of my upcoming blogs very soon.

Hope this will help integrating SCCM and vRA.

Please share and care.

Thanks for your time.


Friday, May 13, 2016

[Updated] Request to extend a chance for VCDX5

virtualpatel.blogspot.com: Request to extend a chance for VCDX5: Hi, I am taking the Liberty here to request VMware Education to extend the chance for Appearing a VCDX 5 Defense after the schedule of Oc...

Tuesday, May 3, 2016

New VMware NSX Licensing Scheme is released

virtualpatel.blogspot.com: New VMware NSX Licensing Scheme is released: Hi all, VMware just announced the new NSX Licensing scheme so please read the FAQ here which has all the preliminary information without...

New VMware NSX Licensing Scheme is released

Hi all,

VMware just announced the new NSX Licensing scheme so please read the FAQ here which has all the preliminary information without even getting panicked and also get in touch with your sales person (assigned to your account) which will give you the better idea.




So by looking at this the most suitable one for any small to mid size organization is the "Advanced" version which has mostly all the bells and whistles except the multi site and Cross VC functionalities.

Its a simple math when making the decisions on what the organization wants. If its ready to spend money to connect their geographically dispersed locations then Enterprise edition is the only choice.

To promote open stack the standard Edition is having the support for it. Home Lab people might have to go for the Standard Edition depending on the price of it as I'm sure it wont be affordable to choose the Advanced or Enterprise version.

IPSEC and SSL VPN  are part of Enterprise which is rising a question on just using L2VPN when normal organization have staff people who are connecting remotely using their MAC/WIN/*NIX machines. So even for that feature they need to go for Enterprise version. Hoping that this should be part of Advanced and NOT Enterprise but lets see what the future might hold.

All the remote features are part of Enterprise which is nice as if you don't need it you don't buy them.

There is no indication on pricing done as the pointer was set to contact the Sales person but even a hint should be fine on the pricing model or even if one has to use just one feature from other edition then what is the cost involved in that (rather than switching from one edition to another completely).

Home Lab people will surely need most of the features to test and try out various scenarios but not sure what will happen in that area unless the person is a vExpert, then its a different story.

This granular model looks adaptive but the pricing model will tell us more on how people feel about it. I just heard that it will be based on 1K per socket but I would not go with it unless it come from a valid source or from VMware itself. So hoping something should be publicly available which will give an idea to the large audience.

Share and care !

Thanks for your time.