Breadcrumbs

Here are the basic steps you can use to transfer or recover FSMO roles during or after migration;

Without going into detail about how this process works, or what it does, If you have just migrated a new Server and are ready to make it the live master for the forrest and domain, simply open up a command prompt (CMD) and enter the following lines in one after the other;

Here are the steps to check if a pc is joined to the domain using Powershell:

3) check results, If it comes back with red text it is a pretty good indicator that there is some form of problem going on, however if it returns “The secure chanel between ‘*’, ‘*dc name*’ and ‘*domain*.local’ is alive and working correctly” then you can continue investigating your problem knowing that the PC is nice and safely connected to the domain.

All that this is now doing is setting the clock to update automatically from a web time server, the servers we are using are the public pool 1, 2 and 3 at ntp.org
We stop and start the time services, and then tell it to resync with the new settings.

It would seem that the last batch of updates from Microsoft around the 12th-14th May 2015 have been causing quite a few PC’s to hang stopping at Update 3 of 3.

This so far looks like it is only affecting Windows 7 Pro X64 based PC’s

As with most IT Professionals, we would never suggest performing a Hard shut-down to your PC, unless there really is no other option, however it does look like in this case this is the only way to fix this particular ‘Stuck Update‘ issue.

If your Windows Update stuck:

Option 1)

Press CTRL + ALT +DEL
This seems to be working for 50% of users encountering this issue, if it does not work then proceed to option 2.

Option 2)

Step 1) Hold down the power button on your PC for 10+ seconds,
Step 2) Restart PC by repressing the power button
Step 3) If confronted with a windows error ‘Your PC did not shut down normally’ screen, select “Start Windows Normally”

Out of the 7 PC’s we have now done this to, all in different environments, we are yet to see any errors or corruptions caused by this. We are continuing to look into which update specifically caused this and why, and so check back later to keep yourself updated.

Ever wanted to check the last boot time of a PC or server?

There are multiple reasons why you may want to find out the last boot time of a server or a PC, Perhaps your server has been restarted without you knowing, and you want to be able to have a starting time to aid in your search through event logs to see what happened prior to the restart. Maybe you are remotely logged onto a PC which is running slow, but the user hasn’t restarted it for a while.

Anyhow, below is how to check the last boot time using either Powershell or CMD:

Ever been stuck with a web browser so full of toolbars or extensions that its almost impossible to do anything? Is your browser unresponsive or you are unable to use the internet?
Then you need to deploy the Windows hidden Cutdown browser:

Here is how to access the web when you can’t use browser.

Simply use the following hotkeys Win+R to open the Run box, then type “hh h” and hit enter

This will bring up the ‘HTML Help’ documentation window,

Right Click and select ‘Jump to URL’

Enter URL of site you need, in this case a copy of RKILL to help get pc back into shape,

See our List of top free products to recover your PC from a virus for more info.

Another way to resolve Logmein Error 4320

As discussed in my previous article on this logmein issue, this error code is most commonly found in a domain environment, or where there may be some form of user lockdown, and may even occur on a multi user non domain PC.

Basically, it is meant to protect the users PC from being accessed by someone other than the logged in user who installed logmein in the first place.

First off, lets open up the logmein Control Panel (Right-Click on the logmein icon in the taskbar, or open from the start menu)

Next we are going to select ‘Options’

Then ‘Preferences’

Select the ‘Security tab’

Click on ‘Show Details’

Click on Browse and select the correct user you want to add to allow access to the PC. You can choose from a list either by selecting the local PC name, or if you are on a domain, then the domain name that the PC is registered with.

Click OK to close all windows, Turn off Logmein then turn it back on,

You are good to go!

Preventative measures could be taken however, When installing logmein, if you do so whilst logged in as a local admin for the PC, this seems to resolve the issue. Please note, this is only for the LOCAL admin for the PC, a domain admin account will most likely not work, and provide the same Logmein error 4320 as discussed above.

So you still have something running on that Virtual XP machine silently consuming space on your HDD?
Finally decided that you need to resize VHD disks to free up wasted storage? Here is how;

1) Turn off your VHD or close any programs that may be running (status should be Powered down)

2) In the Virtual Machines manager, right-click and select settings

4) Select the HDD you want to shrink and click ‘Modify’

5) Then select ‘Compact disk’ and wait.

This process will assess how much space is currently being used, and the, remove the rest leaving 10-20% headroom for growth of the disk. It can take up to 30+ mins to complete this process, so be patient! By using this simple tool, you can shave a good 60+GB of wasted space into freely usable storage.

How to resolve Logmein Error 4320

Whilst setting up logmein for remote access in a pretty locked down domain environment, I have noticed that quite frequently we would get an ‘admin error 4320’ on the remote users PC.

Now the official logmein site would suggest adding users within the logmein interface, which we will cover in ‘Method 2’ however I have found a quicker workaround that works 9 out of 10 times is by simply always running the program as administrator.

Place the Logmein icon either on your desktop or navigate to the program folder path usually “C:\Program Files (x86)\LogMeIn Ignition”

Right click on the icon and select ‘Properties

Once in Properties select the ‘Compatibility’ tab at the top

At the bottom under ‘Privilege level’ tick the ‘Run this program as Administrator’ box*.

If you have more than 1 user on the PC, select ‘Change settings for all users’

Again tick the ‘Run this program as Administrator’ box

OK out of both windows, If logmein is running. Close it again and re-open it, now using an Administrative logon.

Your Logmein error 4320 should now be resolved. if not see the link below