Domain Trust Relationship Failed

Log on to the computer using a local administrator account.

Run PowerShell as Administrator.

Enter the following command to prompt for domain credentials.

$credential = Get-Credential

A security prompt will appear. Provide domain credentials with administrative permissions over the computer account.

Enter the following command to reset the computer account password.

Reset-ComputerMachinePassword -Credential $credential

Close PowerShell and log off.



Understanding the Authenticated Users Group

Authenticated Users isn't a true group—it's a special security principal that specifies any session that's been authenticated using some account, such as a local SAM account, domain account, or account from any trusted domain. So Authenticated Users does include the accounts you mention.

Microsoft created the Authenticated Users group in response to fears that Anonymous logons could gain access to objects for which Everyone (another special security principal) has access. I don't recommend using the Authenticated Users group for controlling permissions because it includes local accounts, which are a bad practice to use because you can't centrally manage them at the domain level, and they use NT LAN Manager (NTLM) authentication rather than the stronger Kerberos. Also, the membership of Authenticated Users changes dynamically when you create a trust to another domain. When you want to give all users in a domain access to a resource, I recommend that you use the Domain Users group, which limits membership to the domain. If you need to give all users in a forest access to a resource, create a universal scope group called Forest Users and add each domain's Domain Users group as a member.


When it comes to permissions, one critical question we need to be able to answer is: which humans have access to a particular resource?

Most of the time when you’re inspecting permissions on a given resource in Windows you’re not dealing with humans (this is actually a best practice); rather, you’re dealing with groups, some of which are built-in implicit identities with ambiguous names. As a result, we often have to do quite a bit of digging to get what we need.


Virtualbox alterar o uuid do harddrive

Erro “UUID Already Exists” ao registrar o HD virtual no VirtualBox

  • Criou uma máquina virtual no VirtualBox;
  • Para criar uma segunda VM e aproveitar a primeira VM como ponto de partida;
    • Copia o VHD/VDI/VMDX e adiciona à nova máquina virtual;
  • Surge o Erro “UUID Already Exists”, porque o VirtualBox cria um identificador único (UUID) para cada disco virtual;
  • Deve ser gerado um novo UUID para a cópia do HDD.

  • Na prompt, executar o seguinte:

    VBoxManage internalcommands sethduuid HDD.vhd


Redshift gui auto start

sudo apt purge gtk-redshift redshift-gtk redshift
sudo apt autoremove

Download RedshiftGUI from sourceforge and install

sudo dpkg -i RedshiftGUI-0.2.4-Linux-x86_64-Fixed.deb
cp -v /usr/share/applications/redshiftgui.desktop ~/.config/autostart/redshiftgui.desktop

How to Make Dropbox Sync My Documents Folder or another folder

Go to the "Start" menu and type "cmd".

Right-click on the "cmd" and choose "Run as administrator".

In the following window, type "mklink /d".

Open the "Dropbox" folder and copy the folder's path.

Paste it into "cmd" window. In the same line, type "<new folder name>". Go to "My Documents" folder and copy the folder's path.

Paste it into "cmd" window. Press "Enter" key and you will see a message – "symbolic link created".

Go to the "Dropbox" folder. Open the "linked" folder. All files from "My documents" folder are synced.

Example: mklink /d "c:\users\test\Dropbox\<folder_name_to_create>" "c:\users\test\Documents"