TUNCAY MERDAN

30 Mayıs 2018 Çarşamba

Sybase / Adaptive Server requires encryption of the login password on the network

Adaptive Server requires encryption of the login password on the network

The below errors are seen when connecting to a Sybase database when "AuthenticationMethod=1" is specified in the DSN.

This is seen when "sp_configure 'net password encryption reqd',2" is run on the Sybase Server.

With "sp_configure 'net password encryption reqd',1" set, no errors are received.

https://knowledgebase.progress.com/articles/Article/000053483

14 Mayıs 2018 Pazartesi

Upgrade Windows 2012 R2 evaluation to full version

C:\Windows\system32>DISM /online /Get-CurrentEdition

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Current edition is:

Current Edition : ServerStandardEval

The operation completed successfully.

C:\Windows\system32>DISM /online /Get-TargetEditions

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Editions that can be upgraded to:

Target Edition : ServerStandard
Target Edition : ServerDatacenter

The operation completed successfully.

C:\Windows\system32>DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX /AcceptEula

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Starting to update components...
Starting to install product key...
Finished installing product key.

Removing package Microsoft-Windows-ServerStandardEvalEdition~31bf3856ad364e35~amd64~~6.3.9600.16384
[==========================100.0%==========================]
Finished updating components.

Starting to apply edition-specific settings...
Finished applying edition-specific settings.

The operation completed successfully.
Restart Windows to complete this operation.

Do you want to restart the computer now? (Y/N)

18 Nisan 2018 Çarşamba

VMware / upgrade the vSphere Replication appliance

Upgrade the vSphere Replication appliance by using a downloadable ISO image

Prerequisites

Upgrade the vCenter Server instance that vSphere Replication extends.
Download the VMware-vSphere_Replication-6.5.x.x-build_number.iso image from the vSphere Downloads page. Copy the ISO image file to a datastore that is accessible from the vCenter Server instance that you use with vSphere Replication.
If the vSphere Replication version that you run is not supported for direct upgrade to vSphere Replication 6.5, upgrade your vSphere Replication instance to a supported version. For example, to upgrade vSphere Replication 5.5 to 6.5, you must first upgrade 5.5 to 5.8.0.2, and then upgrade 5.8.0.2 to 6.1. See the interoperability matrix at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php for solution upgrade paths for vSphere Replication.
Shut down and power off the vSphere Replication virtual machine.

Procedure

Right-click the vSphere Replication virtual machine and select Edit Settings.
If you are upgrading a vSphere Replication Server appliance, reconfigure the virtual machine to increase its memory from 512 MB to 716 MB RAM.
On the Virtual Hardware tab, select CD/DVD Drive > Datastore ISO File.
Navigate to the ISO image in the datastore.
For File Type, select ISO Image and click OK.
Select the option to connect at power on and follow the prompts to add the CD/DVD drive to the vSphere Replication virtual machine.
Power on the vSphere Replication virtual machine.
In a Web browser, log in to the virtual appliance management interface (VAMI).

The URL for the VAMI is https://vr_appliance_address:5480.

Click the Update tab.
Click Settings, select Use CDROM Updates, and click Save Settings.
Click Status and click Check Updates.

The appliance version appears in the list of available updates.

Click Install Updates and click OK.

After the updates install, click the System tab and click Reboot.
After the appliance reboots, start the console of the vSphere Replication virtual machine to monitor the process.

The vSphere Replication appliance reboots two more times for the upgrade procedure to complete.

After the vSphere Replication appliance reboots, log in to the VAMI and repeat the steps to register the vSphere Replication appliance with vCenter Single Sign-On.

This registers the vSphere Replication appliance in the Lookup Service and SSO or updates an existing vSphere Replication registration.

Log out of the vSphere Web Client, clear the browser cache, and log in again to see the upgraded appliance.

https://docs.vmware.com/en/vSphere-Replication/6.5/com.vmware.vsphere.replication-admin.doc/GUID-6DBB9977-DDCF-46CF-94DA-6B8BE683809B.html

VMware / reset root password of vSphere Replication

Reset the root password of vSphere Replication appliance 6.5 (2150038)

Reboot the vSphere Replication appliance.In the Grub screen, press e to edit the current kernel parameters.
Use arrow key to scroll down to this line:
linux /vmlinuz-3.12.62-60 ......... . . . . . . silent quiet showopts
Add this line at the end: init=/bin/bashExample: linux /vmlinuz-3.12.62-60 ..... . . . . . . silent quiet showopts init=/bin/bash"

Press F10 to reboot and vSphere replication appliance will reboot at run level 1.
Mount root filesystem as read write by running this command: mount -o remount,rw /
Run this command to reset the root password: passwd rootAfter the password is reset, reboot the appliance.

Note: If you do not mount root (/) directory as read write (rw) you will receive this error:
passwd: Authentication token manipulation errorpasswd: password unchanged

https://kb.vmware.com/s/article/2150038

16 Nisan 2018 Pazartesi

Hyper-V / Virtual Machine failed to start.

Virtual Machine ' failed to start.

Virtual Machine failed to initialize. (Virtual machine ID EC3DE3E5-F285-4E02-9E85-D325DC6E4212)

Cluster resource 'Virtual Machine ' of type 'Virtual Machine' in clustered role '' failed. The error code was '0x42b' ('The process terminated unexpectedly.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

To disable this fix

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 3 /f

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f

Restart the server for the changes to take effect.

Then enable the fix

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 0 /f