28 C
Dubai
Friday, May 16, 2025
Home Blog Page 57

vCenter Server Appliance Upgrade from 6.0 to 6.5

Lets see how to get the vCenter Server Appliance update from 6.0 to 6.5

image

Run the Installer.exe from the ISO if its a Windows Machine.

D:\vcsa-ui-installer\win32\installer.exe

image

Choose Upgrade –

image

Two Stage Process

Stage 1  – Deploy New vcenter Temp

image

Stage 1  – Enter Source and target info.

If its a same cluster . Mention the esxi info.

image

Enter Target Info –

image

Security Untrusted SSL Prompt – Say Yes.

Enter Temporary vcentername.

image

Choose vcenter Size

image

Enter Temporary IP info. Same VLAN preferred.

image

Choose Finish

image

image

Now you can choose Stage 2- or continue stage 2 using  https://temp-ip:5480

image

Temporary Appliance booted up and ready. _Just _ Good_To_know

image

Take Backups/snapshots of old appliances

image

image

Ignore DRS warnings.

 

image

Vcenter 6.5 is up and ready.

image

 

Known Issue – 1 –

Issue  –  Using same vcenter creds for source and target

Error –

Encountered an internal error. Traceback (most recent call last): File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 2018, in main vmidentityFB.boot() File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 1479, in configureSTS self.startSTSService() File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 1141, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File “/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py”, line 88, in startService return service_start(svc_name, wait_time) File “/usr/lib/vmware/site-packages/cis/utils.py”, line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { “resolution”: null, “detail”: [ { “args”: [ “vmware-stsd” ], “id”: “install.ciscommon.service.failstart”, “localized”: “An error occurred while starting service ‘vmware-stsd'”, “translatable”: “An error occurred while starting service ‘%(0)s'” } ], “componentKey”: null, “problemId”: null }

Solution –

If you use vcenter credentials for Source and Target in the same Cluster.

It will turn of the Source

It will try doing the job on the target using the specified Creds.

Means . Use Esxi Creds for Target creds if its a same cluster.

Known Issue – 2  –

Vcenter Appliance password will Expire.

https://vcenterIP:5480

image

 

Note :

Goodbye vSphere Client for Windows (C#) – Hello HTML5

C# client (Desktop Client/thick client/vSphere Client,vi Client for Windows) will not be available from vcenter 6.5 Onwards

image

[ :ShowExcp:M: 6] 2016-12-05 09:56:31.231 Error: An internal error occurred in the vSphere Client.
Details: Object reference not set to an instance of an object.

Contact VMware support if necessary.
System.NullReferenceException: Object reference not set to an instance of an object.
at VimSearchUI.Services.Impl.SearchSpecBuilderImpl.GetSimpleProperties(PropertyOwner owner, Type parentType)
at VimSearchUI.Services.Impl.SearchSpecBuilderImpl.BuildTypes()
at VimSearchUI.Services.SearchServiceAdaptor.CreateSearchSpec()
at VimSearchUI.Controllers.Impl.SearchController`1.CreateSearchSpec()
at VpxClient.Home.ChromeView.InitializeChromeView()
at VpxClient.Home.ChromeView.OnFirstVimContext()
at VpxClient.Home.ChromeView.set_VimContext(VimContext value)
at VpxClient.Form1.OnFirstVimContext()
at VpxClient.Form1.set_VimContext(VimContext value)
at VpxClient.UI.OnSuccessfulLogin()
at VpxClient.UI.OnLoginEvent(String message, Object[] args)

Azure Active Directory Sync – Choose Specific OUs

Most Common Mistakes. On First Run – Admins – Run Azure Active Directory Sync and Choosing the whole domain/directory to sync.

And later realize they sync so much garbage accounts to Cloud.

Lets see how to cleanup this mess.

Open Azure Active Directory PowerShell.

Set-ADSyncScheduler –SyncCycleEnabled $False

clip_image001

Open Azure Synchronization Service Manager.

Right Click Properties.

image

Choose Containers –

image

Choose the OUs you need who has users and groups and computers which are running windows 10 to leverage azure feature sets

image

Now run a Full Import

image

Now you can see the Deletes –

image

if you see below error

Stopped-deletion-Threshold-exceeded.

Disable (Prevents accidental deletes) – Temporarily. use below command

Disable-ADSyncExportDeletionThreshold

image

Enabled it back (Prevents accidental deletes)

Enable-ADSyncExportDeletionThreshold

Enable Sync Scheduler Back.

Set-ADSyncScheduler –SyncCycleEnabled $True

Reset root password vCenter Server Appliance 6.0

Forgot root password to vCenter Appliance 6.0

Most of the Cases –

  • Gets Expired by default.
  • Locked out by Wrong Attempts

Lets see how to change the root password –

  • Reboot the vCSA 6.0 using the vSphere Client.
  • When the GRUB boot loader appears, press the spacebar to disable auto boot.
  • Press P to Enter Edit Mode

image

image

If the vCSA was deployed without editing the root password in the Virtual Appliance Management Interface (VAMI), the default GRUB password is vmware.

If the vCSA root password was reset using the VAMI, then the GRUB password is the password last set in the VAMI for the root account.

Choose the Second One.  kernel /…

image

Type e to edit the boot command.

Append

init=/bin/bash

to the kernel boot options.

image

  • Press Enter. The GRUB menu reappears.
  • Type b to start the boot process. The system boots to a shell.
  • Reset the root password by running below command.
    passwd root

image

image

Restart the appliance by running the reboot command.

Set Password Never Expires – 

Login to Appliance

https://10.10.10.100:5480

image

Copy Active Directory Group members to new group

Migrating Members from Old group to New group in Active directory

image

image

Group Attribute Editor – Collect DistinguishedName Value for Old and New Group

image

Open PowerShell in Directory Server

Import-Module Activedirectory

$oldgroup = Get-ADGroup "CN=OLD_Group,OU=02 Groups,DC=Cloudid,DC=biz"
$newgroup = Get-ADGroup "CN=New_Group,OU=02 Groups,DC=Cloudid,DC=biz"

To Test – (-Whatif)

Get-ADGroupMember $oldgroup | foreach{Add-ADGroupMember $newgroup -Members $_.distinguishedName -WhatIf}

Remove –Whatif to Execute it.

image

To Execute –

Get-ADGroupMember $oldgroup | foreach{Add-ADGroupMember $newgroup -Members $_.distinguishedName}

image

You can see members migrated to new group

image

550 Address unknown – Sophos UTM 9

From Office365/Gmail fails to Exchange On-Premises

External to Internal Mails 550 Address unknown

Anti-spam Sophos UTM 9

NDR From Office 365 to Exchange 2010/2013/2016 On Premises –

image
Original Message Details
Created Date:
11/8/2016 4:25:50 PM
Sender Address:
test@external.com
Recipient Address:
user@careexchange.in
Subject:Test333
 
Created Date: 11/8/2016 4:25:50 PM
Sender Address: test@external.com
Recipient Address: user@careexchange.in
Subject: Test333
Error Details
Reported error:
550 5.0.350 Remote server returned an error -> 550 Address unknown
KL13306MB1655.apcprd06.prod.outlook.com
DSN generated by:
Remote server:
mail.careexchange.in
Reported error:
Reported error: 550 5.0.350 Remote server returned an error
-> 550 Address unknown
DSN generated by: KL13306MB1655.
apcprd06.prod.outlook.com
Remote server: mail.careexchange.in

NDR From Gmail to Exchange 2010/2013/2016 On Premises –

Delivery to the following recipient failed permanently:

user@careexchange.in
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain careexchange.in by mail.careexchange.in . [81.13.83.22].
The error that the other server returned was:
550 Address unknown

—– Original message —–
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:from:date:message-id:subject:to;
bh=dZ+ndmdI1p6cWqUcsfJgQOCj3fZJYQi48MT/FaXgX8g=;
b=Nk6rN0yWdwctAitjOJt8nmNInBfI7PcjXy2tf2DGL6MRVX 4kvGcU6gOlhk3v3sxjBs
3+JD31IxI+m33333333333333333QJfJ4/YmonoDQrymlBLiL5Z WJfe0kVuisrrnbws650cEA3NWgin2T8LFomQXsymcImucrndNAU 2hJXn4ijIDDhNMKHHINKu3
33333333333333333333333333333333333/h37XFiPTX69
j4zuGUZie5lUu9XKpxCs/u/VVzr5DXJw8zkN9GuMFMXZgRFJxa8 qUni67CQwqEfNfwUM
n9wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=dZ+ndmdI1p6cWqUcsfJgQOCj3fZJYQi48MT/FaXgX8g=;
b=brbRKkaNqFja0Mn0H3333333333333j44FpKUYCgn1NHk IslBpQbA0QGZNdala
XJT6mqu8f9t2KlVy5OiN71vZ+XmY4ZxPUVNj5jb8LzbaklCO5 TXU1RDjx8FqupA1lRLv
GObo/NW941kln+DwoXk9333333333333333+jBXvc1GeDPCU NBj9OWPUdfinOqe
sAD3FHfh35DETPskq1hYcl7X/zHfAnvLK6T4jqsWMo6e5NR 89brdp0tdzTlT1IwAPT3G
rF/IecyK+uEHDF6lcHM8NG+yPN2EQ6prwAlIlSVZwvSlUC2R/ 7EHkN6xwbLoB6Dzr8l/
/5EQ==
X-Gm-Message-State: ABUngvfPYs55pDPkjNAB2zR/O8vG7A/uxJlTIuQRO9vgy8onWU Ub8HXNwhPqasz4SZvmjCCXmeGrZk2C/JP9hg==
X-Received: by 10.31.107.135 with SMTP id k7mr8987043vki.119.1478625038433;
Tue, 08 Nov 2016 09:10:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.67.70 with HTTP; Tue, 8 Nov 2016 09:10:38 -0800 (PST)
From: user@gmail.com>
Date: Tue, 8 Nov 2016 09:10:38 -0800
Message-ID: <CAHHVjUVTJefrH-i33333333333333yLwvbAvZSLdiFWObg0KZ-98a3yYA@mail.gmail.com>
Subject: 22
To: user@careexchange.in
Content-Type: multipart/alternative; boundary=001a133307da0540cd38a3

vGcU6gOlhk3v3sxjBs
3+JD31IxI+m33333333333333333QJfJ4/YmonoDQrymlBLiL5Z WJfe0kVuisrrnbws650cEA3NWgin2T8LFomQXsymcImucrndNA U2hJXn4ij IDDhNMKHHINKu3
33333333333333333333333333333333333/h37XFiPTX69
j4zuGUZie5lUu9XKpxCs/u/VVzr5DXJw8zkN9GuMFMXZgRFJxa8q Uni67CQwqEfNfwUM
n9wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=dZ+ndmdI1p6cWqUcsfJgQOCj3fZJYQi48MT/FaXgX8g=;
b=brbRKkaNqFja0Mn0H3333333333333j44FpKUYCgn1N HkIslBpQbA0QGZNdala
XJT6mqu8f9t2KlVy5OiN71vZ+XmY4ZxPUVNj5jb8LzbaklCO5T XU1RDjx8FqupA1lRLv
GObo/NW941kln+DwoXk9333333333333333+jBXvc1GeDPC UNBj9OWPUdfinOqe
sAD3FHfh35DETPskq1hYcl7X/zHfAnvLK6T4jqsWMo6e5NR89 brdp0tdzTlT1IwAPT3G
rF/IecyK+uEHDF6lcHM8NG+yPN2EQ6prwAlIlSVZwvSlUC2R/7 EHkN6xwbLoB6Dzr8l/
/5EQ==
X-Gm-Message-State: ABUngvfPYs55pDPkjNAB2zR/O8vG7A/uxJlTIuQRO9vgy8onW UUb8HXNwhPqasz4SZvmjCCXmeGrZk2C/JP9hg==
X-Received: by 10.31.107.135 with SMTP id k7mr8987043vki.119.1478625038433;
Tue, 08 Nov 2016 09:10:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.67.70 with HTTP; Tue, 8 Nov 2016 09:10:38 -0800 (PST)
From: user@gmail.com>
Date: Tue, 8 Nov 2016 09:10:38 -0800
Message-ID: <CAHHVjUVTJefrH-i33333333333333yLwvbAvZSLdiFWObg0KZ-98a3yYA@mail.gmail.com>
Subject: 22
To: user@careexchange.in
Content-Type: multipart/alternative; boundary=001a133307da0540cd38a3

Solution –

Disable Recipient Verification on Sophos UTM 9 Email Protection.

image

After a Physical to Virtual Conversion – Key not Valid for use

After a Physical to Virtual Conversion using P2v Converter VMware , Generic Applications gets below Error on startup

System.Security.CryptoGraphy.CryptographicException: Key not Valid for Use in Specified State

image

System.Security.CryptoGraphy.CryptographicException: Key not Valid for Use in Specified State

at System.Security.CryptoGraphy.Utils.CreateProvHandle(CspParameters Parameters,Boolean RandomkeyContainer)

Solution :

Moved this SID Named folder to a different location.

C:\Users\Administrator\AppData\Roaming\Microsoft\Crypto\DSS

clip_image001

× How can I help you?