GaelV's Posts

Hi Community I'm used to deploy new VM from template with Customization Specification Manager file I made under vCenter 6.5U3 GUI. For automation purposes, i'm trying to make PowerCLI (.p... See more...
Hi Community I'm used to deploy new VM from template with Customization Specification Manager file I made under vCenter 6.5U3 GUI. For automation purposes, i'm trying to make PowerCLI (.ps1) scripts to ease VM deployment, right now i'm just at a test step (line by line execution) and just encounter a problem. Template details : - OS Type : Windows - Take the VM name as Windows' computer name - Time : GMT +01:00 - 1x NIC who prompt user for IP adress only  (VLAN + netmask + gateway + DNS are already set in the template) - add the vm into AD Domain - Do not log in automatically as Administrator - Sysprep +  generate new SID - Registration info  : user : xxxx + Organization : xxxx - Username and password already set too My issue is  that I'm able to deploy a new VM from template using PowerCli, but when I set -OSCustomizationSpec parameter to use my template, it didn't ask me the IP address, and it doesn't seems to use the VM name as Windows' computer name. It doesn't seems that i can 100% use the template which was created on vCenter GUI.. Is there a problem from my CLI deployment or a known bug ? Do I have to recreate again the same template but for CLI ? Thanks
Hi M0n1t0r If you can, do the following things : 1) Update your server with the Service Pack For ProLiant from HPE (i used the 2019.03.1 and it works) 2) Update your ESXi 6.7 to the build 13... See more...
Hi M0n1t0r If you can, do the following things : 1) Update your server with the Service Pack For ProLiant from HPE (i used the 2019.03.1 and it works) 2) Update your ESXi 6.7 to the build 13981272 (aka  ESXi670-201906002) Let me know if you still encounter issues Regards, Gael
You just add to go on your vCenter Web Client through the Datastore tab , then clic on the datastore you want, then clic on the VM tab and the VM that currently using the datastore appears... or ... See more...
You just add to go on your vCenter Web Client through the Datastore tab , then clic on the datastore you want, then clic on the VM tab and the VM that currently using the datastore appears... or not. This is the same manipulation to know which host is currently using the datastore if you clic on Host tab. A little screenshot to explain :
Hi, Have you any solutions about this subject ? cause i have the same with too many warning mail sent everyday..
Still the error on HP ML350 Gen10 VMware ESXi, 6.5.0, 10884925 ...
Indeed, that's strange.. I think ESXi Shell and SSH are both enabled ?
Hi, I had the same issue one day, i made a mistake so maybe you too 1) When you start WinSCP by default, the file protocol is SFTP. ESXi allowed SFTP but sometimes it crashes or doesn't ... See more...
Hi, I had the same issue one day, i made a mistake so maybe you too 1) When you start WinSCP by default, the file protocol is SFTP. ESXi allowed SFTP but sometimes it crashes or doesn't function well. 2) You have to choose the SCP file protocol then click Login. 3) Everything has to work fine !
Still have the problem ? Any ideas ?
Major Version is 6.1.8.31 and minor is 7.2.80.155_6.1.8.31
Hi community ! I just face a big issue maybe a known issue, while I was checking my VDP jobs. Here's my infra: vCenter 6.5U2 + VDP 6.1 + ESXi 6.5U2 - My backup job was made to save 25VMs ... See more...
Hi community ! I just face a big issue maybe a known issue, while I was checking my VDP jobs. Here's my infra: vCenter 6.5U2 + VDP 6.1 + ESXi 6.5U2 - My backup job was made to save 25VMs from a cluster of 5 ESXis. - The backup job unticked (2 weeks ago...) 20/25VMs it has to save. - Crossing the email log + events that happened last 2 weeks on ESXi and vCenter; i think the backup job losts what it has to save due to VM vMotion. By the way, some of the "losts" VM have RDM disk, others have regular disks like vmdk (virtual disk). Do some of you have already faced to this issue ? Thanks for reading/answering
So when the 1st task "Copy data from source vCenter Server to target vCenter Server" is complete, the Migration Assistant has done it's job and shuts down with the source vCenter Server? => you ... See more...
So when the 1st task "Copy data from source vCenter Server to target vCenter Server" is complete, the Migration Assistant has done it's job and shuts down with the source vCenter Server? => you have to complete Stage 1 and 2 to exit the Migration Assistant (if it doesn't exit itself), take a look at those screenshots : Migration vCenter Windows vers PSC 6.5 | VroomBlog  The installer then carries on with task 2 "Setup target vCenter Server and start services and then task 3 Import copied data to target vCenter Server. => yes Essentially the source is no longer needed as the target has all of the information it needs. Presumably from the Migration Assistant, which can now shut down. => no is no longer needed but i advise you to keep it in backup for weeks if you encounter a big issue or if you need to restore it for any reason.. In any cases, if you can access to the VCSA web client it means the deployment is over, so you can close the migration assistant if it's not already.
Indeed it's a normal behaviour. Once it's done the VCSA appliance got the same FQDN and IP address as the source vCenter.
Alright, I advise you to let the Migration Assistant opened until the migration is completed because once the migration is done, it can ask you some informations.
Hi, Before any new beginning you have to mind the following informations : 1) check if your windows version is compatible with the vCenter server version you want to update to => VMware Knowl... See more...
Hi, Before any new beginning you have to mind the following informations : 1) check if your windows version is compatible with the vCenter server version you want to update to => VMware Knowledge Base 2) Check if one of your ESXi has enough resources to host temporary 2 vCenter (the old one will be shutdown by the end of migration) 3) Reserve a temporary name and IP address (only if you want to update to VCSA (Linux) Then, 1st step : You have to mount the ISO on your actual/source vCenter server, then go to the folder Migration Assistant on D:\ then run the "VMware-Migration-Assistant.exe". It will opens a CMD window, let the precheck run until it mentions that's ok you can migrate. 2nd step : Once done, go to your PC or a third part device. Mount the ISO on your computer then go to D:\ to the folder "vcsa-ui-installer\win32\" then lauch "installer.exe" Let me know if it works
Hi, you got the white screen while log into web client or into the vcenter VM console ?
RickVerstegen​ , i set up a Log Insight with my vCenter Licence (25 OSI as you said) but it seems really too much compare to my infrastructure size. I'll check out if there's basic use and con... See more...
RickVerstegen​ , i set up a Log Insight with my vCenter Licence (25 OSI as you said) but it seems really too much compare to my infrastructure size. I'll check out if there's basic use and configuration for Log Insight.
RickVerstegen​ is this still working for ESXi 6.5 ? because I did it years ago on vSphere 5.1-5.5 environment but I thought it didn't work anymore.
Hi ! I've just migrate our vCenter 6.0 (Win 2008) to the VCSA 6.5. I check some settings and there's something missing. In vCenter 6.0 i had the SysLog Collector so i was able to centraliz... See more...
Hi ! I've just migrate our vCenter 6.0 (Win 2008) to the VCSA 6.5. I check some settings and there's something missing. In vCenter 6.0 i had the SysLog Collector so i was able to centralize ESXi logs here. But in VCSA 6.5 , there's no more this setting : It seems there's something to do with Log Insight or something ? Is there any "free" possibility to have this setting back again ? Thanks all Gael
The solution is you have to mount the ISO on your Local PC (as a third part material) then launch the Migration Assistant. If your source vCenter is Windows Based you have to launch the Precheck... See more...
The solution is you have to mount the ISO on your Local PC (as a third part material) then launch the Migration Assistant. If your source vCenter is Windows Based you have to launch the Precheck program on CMD. Once, the migration will run automatically. BE CAREFUL, you don't have to close the Migration Assistant in your computer until it finish. Then you'll be able to set the source/destination vCenter information
Hi community I'm dealing with vSphere 6.0 for a while but i've just experienced a new issue on a VMFS Datastore. First issue : I'm trying to Move an iso file to a different folder on ... See more...
Hi community I'm dealing with vSphere 6.0 for a while but i've just experienced a new issue on a VMFS Datastore. First issue : I'm trying to Move an iso file to a different folder on the same datastore. First when i click on "Move to..." menu , it show a Copy action on vCenter's Recent Tasks and it takes too much times (more than 45min for a 4GB iso... Second issue : Once the file is copied/moved i don't know which word i have to use, the file is still present on the source and destination folder and i can't delete from the source folder. I have the Unable to access file....error. Then when i succeed to delete it, it delete both iso (source and destination..) Third issue : I can't move/copy file without the Unable to access file...error Is there something i missed ?