Showing posts with label Password. Show all posts
Showing posts with label Password. Show all posts

Thursday, 21 September 2017

Upgrading a Windows 2008 Server to 2012 R2 Standard

We have a client, Population Services International Liberia (PSI). All of their ICT infrastructure is being managed by us as a consultant.

There’s a file sharing server (HP ProLiant Server T620) that has been configured and setup for years running Windows Server 2008 R2 Standard. Last week, I was forced to upgrade the (OS) Operating System to Windows Server 2012 R2 Standard for below reasons.

I have had issues with RAM failure twice in the past and the RAM was replaced.

A monthly preventive ICT maintenance is also carried out on all their IT equipment including Anti-virus full system scan, defragmentation of disk space, deleting temporary internet files, Windows updates, checking all wireless access points, switches & routers, making sure everyone is seamlessly browsing the internet and system backups in case of disaster recovery or any other future problems.
One morning, I was just back in office from one of our clients sub office out of Monrovia, Sanniquillie Nimba County and doing the routine checks. I got an email request from PSI to creating new users and access to the said file sharing server. To be specific, Human Resource Department folder. I quickly arranged my tools and left for their site.

I typed in the administrative password for the server and got an incorrect password warning over and over. I couldn’t believe it because even if you woke me up at night I could read it out loud. I phoned the guy who’s in charge of the server room keys and whom I relate every sensitive information including Wi-Fi password, desktop administrative passwords, including the server just in case I am unable to get there on time due to emergency if he made any changes on the server password. He responded that yes he did, but can’t remember where he place it neither remember. I was so frustrated that why would he make changes without securing a system password or sharing it with me. I had no alternative but to get Windows Server 2012 software in resetting my password. Now if you don’t have this idea you will end up running a fresh installation, structuring files, configuring Active Directory, Windows Server Update Services (WSUS), and creating all users over. This would have been more than a pain.

These steps are very easy and simple to follow once you have your software installation disk or USB available. (Windows Server 2012 R2 Standard)
·      Boot from you Microsoft Windows Server 2012 DVD
·      From the Windows Setup menu, Click “Next’’.
·      Select “repair Your computer’’
·      Under Choose and option, click on “Troubleshoot”.
·      Under Advance option, click “Command Prompt”.

At the command prompt, run the following commands:
  • d: and hit enter
  • cd windows\system32 and hit enter
  • ren Utilman.exe Utilman.exe.old and hit enter
  • copy cmd.exe Utilman.exe

·      Close the command prompt and click “Continue.

·     The server should boot and display a logon screen. In this case you only hold Windows Key + U.
·     At the prompt you can now change the password you wish by entering the following commands:
net user administrator ‘’Adm1n1str8t1ve” for example.

Close the command prompt, you will now be able to log back onto the server using the password you entered in the command prompt. Once you verified that you can log on to the server. That’s really cool. You still need to repeat the steps in getting to the command prompt by restarting the server and running these commands:

          · d: and hit enter
          · cd windows\system32, and hit enter
          · ren Utilman.exe Utilman.exe.new, and hit enter
          · copy cmd.exe Utilman.exe

Here are photos of my password reset. The server is now running without causing any inconvenience to our customers.

Reach out for NATC for all your IT needs and support!

Prepared by:
Daniel W. Collins
Senior IT Technician

New Africa Technology Company (NATC)

Thursday, 13 April 2017

How to Reset Your Forgotten Password in Windows 10

I am Farman Elahi, IT Technician of New Africa Technology Company. A week ago, I was finally successful in reset forgotten password for Windows 10. Before few days a call came from Social Impact.


To reset the password using this method, insert your Windows installation disk and boot from it. Once you are in the setup screen, press the keyboard shortcut “Shift + F10” to launch the Command Prompt.


Once the Command Prompt has been opened, copy the below commands and execute them one after the other. All we are doing is replacing “utilman.exe” with “cmd.exe.”

Type Diskpart Press Enter. Than Type List Volume press Enter.


On my system F: is system Drive. Check your system drive.
Type move.utilman.exe utiman.exe.bak press Enter
Type copy cmd.exe utiman.exe.bak Press Enter



Once logged in, you can reset the other account’s password from the Local Users and Groups window. You can access it by entering “lusrmgr.msc” in the run dialog box (Win + R)

Farman Elahi
IT Technician NATC

Tuesday, 5 April 2016

IP Conflict

By Daniel Collins

Image from here.

Every Computer or device on a network must have a unique IP address. Routers, Switches and Servers are assigned with “static” IP addresses. This allows a network administrator to carry out smoother troubleshooting in case of any issues.

I was sent to one of our client’s office to resolve an issue where the user could not connect to her department folder on their file sharing server. I was there from morning to the afternoon figuring out on how to solve this problem. I asked the lady to give me access to the server room which she did, but she didn’t have the password to log in to the server.

Because I knew the server’s IP, I started to ping the IP address of the server using Windows command tool. I realized that the device using this IP was active. I was thinking, but how can I ping the server’s IP but cannot access it? This meant that the IP address I was pinging was assigned to another device and not the server.

After I went back in the lady’s office, I saw a newly installed MikroTIK router connected to the network. I asked the lady, this is new, when was this setup? She replied… ‘’ The ISP just dropped it in this morning.’’

Then, I turned on my laptop connected it to the network, opened my web browser and typed in the IP address of the server again… ‘192.168.12.7’. This logged me directly into the MikroTIK router! My suspicions were proven to be correct. Then it was easy.

I resolved the issue by changing the static IP on the MicroTIK device from 192.168.12.7 to 192.168.12.13

The IP conflict was resolved. All I did was to restart the server and the router in resolving the issue.
The lady could now continue her work.


Again, NATC saves the day!