Here is an easy fix to solve the broken relationship between your workstation and the Domain Controller.
Error message at logon : The trust relationship between this workstation and the primary domain failed
- Logon locally with the Administrator account : “.\Administrator“
- Run Powershell as Administrator
- Run the following to prompt you to enter your Domain Admin user account credential
$credential = Get-Credential
- Finally, run the following to reset your AD Computer Password
Reset-ComputerMachinePassword -Server <DomainControllerName> -Credential $credential
You should now be able to log you in as a Domain User.
Today, I had to clone an Oracle server several times. I will not explain the steps but just let you know what I had to do to get Oracle working after this change.
The Listener service won’t start. I had to edit its configuration to match to new Server name.
- Open the Listener configuration file : “C:\app\oracle\product\12.2.0\dbhome_1\network\admin\listener.ora”. Could be different depending on your installation settings.
- Replace the old Server name by the new one.
- Starting the Listener won’t allow me to connect. I also had to restart completely the Server.
When running vCenter Server, you can clone the VM and it will prompt you for new customization settings.
Without it… You will need to manually copy the VM files (or only the VMDK if you attach it to a newly created VM). Then run Sysprep to configure it and avoid duplicate SID.
- Shutdown your VM and copy its files or VMDK to a new folder on the current or new Datastore. If you want to rename the VMDK file, copy it using “vmkfstools”.
vmkfstools -i /vmfs/volumes/server/server1.vmdk /vmfs/volumes/datastore1/cloned-server/server2.vmdk -d thin
- Create a new VM and attach the cloned VMDK. If all files have been copied, just register the VMX file to the Inventory.
- Boot up the VM and run Sysprep :
sysprep /oobe /generalize /reboot
Tips : You can use the switch /shutdown to turn it off after customization and then convert it to a VM Template if needed.
- VM will reboot and ask you for customization settings.
Another and easier way to accomplish this task is to use VMWare vCenter Converter Standalone during the “Convert Machine” GUI. Or if you forgot it, you can do it through the “Configure Machine” GUI.
Open the “FilieZilla Server.xml” file located in the program installation folder.
Find the tag <Item name=”Admin Password” type=”string”>***</Item> which contains your Server Password.
Download issue resolved by adding the MIME type .esd (application/octet-stream) into IIS.
Edit : it seems it only solve the download issue. Following update and steps have to be done. This should also update WSUS and add the MIME type .esd.
Once download is completed, client was unable to install the upgrade; error 0xc1800118.
- Install KB3159706 from Windows Update Catalog and follow the following steps from MS Support :
- Check the WSUS Db and repair it :
Edit : Finally, I ended by recreating the SUSDB as the above did not work and CU 1703 won’t install.
I faced an issue where a Trusted Domain could not access Shares on our main Domain.
Error message: No logon server available to service the logon request
Error only happened from the Trusted Domain, everything’s fine internally.
The server hosting the Shares showed up Audit Failure logs in the Event Viewer like:
Failure Reason: An Error occured during Logon.
Sub Status: 0x0
I logged on to my DC, opened up the MMC “Domains and Trusts” and received an error message. Reboot the DC solved it…
Scan system for disk:
Get disk info:
Show VG and linked PV:
Show PV info:
pvdisplay -v /dev/dsk/c3t2d0
Check for disk IO error or successful read:
dd if=/dev/rdsk/c3t2d0 of=/dev/null bs=1024k
Enable VG if needed:
vgchange -a y /dev/vg00
Show mount point:
You are also able to manage disk using “sam”.