Tachytelic.net

How To

How to add Open command window here to Windows 10 Context Menu

by Paulie Leave a Comment

Time needed: 2 minutes.

The context menu open command window here has been replaced in Windows 10 by Open Powershell window here. Here is how to restore the command window here option:

  1. Open Registry Editor

    Press Windows Key + R to open the run dialog. Then type regedit and click ok.
    Image showing run dialog in Windows 10 to open the registry editor

  2. Navigate the registry

    Go to:
    HKEY_CLASSES_ROOT\Directory\shell\cmd

  3. Access Permissions of the cmd key

    Right click on the “cmd” key and then click on permissions.

  4. Modify Permissions

    In the permissions window, click advanced. Click the change link at the top of the advanced window next to the current owner.

  5. Change the owner of the registry to your own user account

    Type your user account name (or search for it) and click “Check Names”. Then click OK.

  6. Replace owner on Subcontainers

    Tick the box that says “Replace owner on subcontainers and objects

  7. Modify Permissions

    Back in the main permissions window, change the permissions for Administrators to “Full Control”

  8. Modify the HideBasedOnVelocityId registry key

    In the right hand pane, right click on HideBasedOnVelocityId and click on rename. Rename it to ShowBasedOnVelocityId

  9. Shift and Right Click on any Folder

    Quit registry editor and try holding down shift and right clicking on any folder. You should now see the option to open command window here.

Here is a video showing how to do it in case the above was not clear:

Add an additional hard drive to virtual SCO Openserver 5

by Paulie 3 Comments

This is a quick post and video that shows how to add an additional Hard Drive to a Virtual SCO Openserver 5 system.

When I configure SCO Openserver Systems I always use the LSI Logic Parrallel controller. It seems to provide reasonable performance and makes it easy to add additional virtual drives if required.

The virtual machine in the video already has two SCSI drives and I demonstrate how to add a third. When completed the /etc/conf/cf.d/mscsi file looks like this:

*ha     attach  number  ID      lun     bus
*
lsil    Sdsk    0       0       0       0
wd      Srom    1       0       0       0
lsil    Sdsk    0       1       0       0
lsil    Sdsk    0       2       0       0

The highlighted line represents the virtual disk that is going to be added. Note that in the mscsi file an asterisk symbol denotes a comment. So this virtual machine has 3 hard drives, all using the “lsil” controller at IDs 0,1 and 2.

How to add an Additional Virtual Drive

Adding an additional drive is easy, but not very intuitive in my opinion. Here is how to do it:

  1. From a root prompt run:
    mkdev hd
  2. Choose Option:
    2) Add a hard disk to a SCSI controller
  3. You are now prompted for the prefix of the SCSI Host Adapter that will support the new drive. In this case it is “lsil”. You can just press enter if that is already the default.
  4. When asked which SCSI Host Adapter supports the new device (0 or 1). Put in whatever you specified on the Virtual Hard Drive. But more than likely it will be zero.
  5. Next you are asked what the Target ID for the device is. Again, match this to the SCSI ID specified with the Virtual machine.
  6. The LUN will be Zero.
  7. Finally you are asked if you would like to update the SCSI configuration. Press y for Yes.

Now relink the kernel and reboot. When you have logged back in run the procedure above and answer the questions in the same way again. This time around “mkdev hd” actually does some work with the drive.

From here it is up to you how you want to setup the drive, but in a ESXi environment I always just make a single division and use the entire drive for Unix.

After the new drive is added and you have created a division you can mount it with scoadmin.

It is far easier to watch the video below than understand the written explanation. If you have any questions, feel free to ask.

Disable Pause Updates for 7 days feature of Windows 10

by Paulie Leave a Comment

The May 2019 update of Windows 10 (version 1903) introduced a new feature which allows users to Pause Updates for 7 days. This post covers how to disable that feature in a domain environment.

Update ADMX Templates from build 1903

At the time of writing this post, Microsoft have not made an updated ADMX template bundle for the May 2019 update of Windows 10.

So the easiest (but maybe not ideal) solution is to copy the ADMX files from an updated Windows 10 machine to your central store, you can find them in:

C:\Windows\PolicyDefinitions

Simply copy the contents of the folder into your domain controller, most likely in:

C:\windows\SYSVOL\domain\Policies\PolicyDefinitions

Make sure that you copy the definitions from an updated version of Windows 10, check the version using these instructions.

If you do not have easy access to the files, I have made them available here. But please understand that the zip file contains only the en-US and en-GB folders, so if you need another language then this download will not be suitable for your environment:

Edit Group Policy Settings to disable the Pause Updates feature

Once you have updated the Policy Definitions on your domain controller, you will be able to disable the pause updates feature by doing the following:

  • Open Group Policy Management
  • Create and Link a new Group Policy or edit an existing one which targets the machines you want to edit the behaviour on.
  • Navigate to:
    • Computer Configuration
    • Policies
    • Administrative Templates
    • Windows Components
    • Windows Updates
  • In the right hand pane, double click on:
    Remove access to “Pause updates” feature
  • Set it to “enabled” to disable access to the feature.

Now you can either reboot or force a group policy update and the option to pause updates will have been disabled.

How to change the default Dell iDRAC Password

by Paulie 1 Comment

The Dell iDRAC is so useful for many things, but in its default configuration it is very insecure:

  • The default username is “root”
  • The default password is “calvin”

In this post I will show you how both rename the root account and change the password.

Renaming the root account adds a layer of obscurity making it more difficult for unauthorised users to gain console level access.

How to rename the iDrac root account and change the password.

  • Login to the iDRAC using your credentials or use the default if they have not been changed
  • On the left hand menu, choose “iDRAC Settings” and then “User Authentication”:
  • Click on the User ID that corresponds to the root account, to edit it:
  • The default action of “Configure user” should already be selected, so click on “Next”
  • Change the username as per your preferences and set the new password:
  • Scroll to the bottom of the page and click apply.
  • Log-out of the iDrac and check your new settings.
Exit mobile version