Showing posts with label Command Prompt. Show all posts
Showing posts with label Command Prompt. Show all posts

Wednesday, January 2, 2013

BIT LOCKER IN WINDOWS 8: LOCKING AFTER UNLOCKING THE DRIVE WITHOUT RESTARTING THE MACHINE

Bit Locker can do wonders..
But when I configured Bit Locker for one of my drives in Windows 8, though it worked smoothly, I faced a real problem!!!!!

I can unlock the Drive.
But...............
I can not lock it.. 
My Bit Locker Encrypted drive remains open, until I restart my Lap.

Tried a lot in many of the sites including the following:-

http://scorpiondivine.blogspot.in/2012/01/how-to-relock-bitlocker-encrypted-drive.html
http://jonamafun.blogspot.in/2009/11/how-to-re-lock-bitlocker-drive.html

I sincerely thanks the efforts put in by both Bloggers.

But, things didn't work for me.
Finally, after a lot of investigations, i found out the real reason is the Villain named "Elevated privileges".

Anyway, I worked it out my way, with inputs from the above site and I am sharing these for you...!

STEP-1
Copy the following which is in RED and paste it on a Notepad file.

manage-bde -lock G: -forcedismount  

Please take a note to replace the G: with the corresponding one of your Bit Locker drive Letter.

Save the Notepad as lock.bat 

Copy this file to the C:\Windows folder.

STEP-2

Now Copy the following which is in BLUE and paste it on a Notepad file.


Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Drive\shell\runas]
@="Lock"

[HKEY_CLASSES_ROOT\Drive\shell\runas\AppliesTo]
@="G:\\"

[HKEY_CLASSES_ROOT\Drive\shell\runas\command]
@="runas /user:pradeep\\administrator /savecred c:\\windows\\lock.bat"

make the following changes:-

In the  @="G:\\" part, put the Drive Letter of your Bit Locker drive. Eg. @="D:\\"

In the @="runas /user:pradeep\\administrator /savecred c:\\windows\\lock.bat" part,
pay attention towards,user:pradeep\\administrator.
pradeep is my Computer Name.
You have to replace pradeep with your Computer Name (You can check it by Right clicking My Computer Icon on your Desktop and Selecting properties. Else, you may type sysdm.cpl in RUN or COMMAND PROMPT and press ENTER, you will get the Computer Name).

After theses changes, save the Notepad as lock.reg somewhere on desktop.

STEP-3

Now, double click the lock.reg file. It will give out some warnings, don't worry, Click YES and you will get a Completion Message and Click OK

STEP-4
 
Now go to Command Prompt or RUN, type lusrmgr.msc and enter.
you will get a Console Window for Users and Group. It will look like the below given picture. (Click on the picture to enlarge it.)

STEP-5

Right Click on the Administrator and Select Properties.
remove the tick mark in front of "Account is Disabled".
It should look as follows:-






















Click Apply and OK.

STEP-6

Now, Right Click the Administrator and select Set Password.
There will be a Warning Message as follows:-













Click Proceed and the next window opens:-















Give a Password of your Choice in the First Space and repeat the same in the next space.
Click OK.
You will get a Confirmation that the Password is Set. Click OK.

STEP-7

Restart your Machine.

Unlock your Bit Locker drive with your password.

STEP-8

Now Right Click the Bit Locker Drive.......
You will see...

 

 









A selectable "Lock" in the context.
Click the "Lock".
the following appears..

Type the password which you have given in STEP- 6.
You will not be able to see what you type, so please be careful to give the correct password.

A black screen pops up...... and ..
Your Drive is Locked....!

That's all...
----------------
For any clarifications, doubts, please mail me at pradeepthegreat2010@gmail.com.
I will be more than happy to help.

Thank You and if you like the post, please Join this site.


Saturday, December 25, 2010

"Setup Cannot Copy the File Staxmem.Dll" Error Message

"Setup Cannot Copy the File Staxmem.Dll" Error Message
My god... It almost landed me in the midst of nowhere.
I was performing a repair of Windows XP and at a particular point, I got stuck up.
This staxmem.dll problem.


I could see the file in i386 folder of the CD as well as in Directory... but the copy error remained despite of my efforts to get the file from alternate locations.
Then I consulted Google- my ultimate Guru- and found so many pages with such problems.
Mostly answered by MVPs and other Masters of Computer Scince........ but all the solutions lead me again to the same dead end.
In fact, his was not the answer exactly I needed to my problem, but something like that .
So, I derived a way out of that solution to solve my problem.
Here during the installation, I activated a Command Prompt.
(How to do that...? See my Next Post....!)
Now give the following command on the Command Prompt:-
esentutl /g %windir%\security\database\secedit.sdb
Enter
Now things happen as you see in the fllowing screenshot.

Now give the next command in the Command Prompt:-
esentutl /p %windir%\security\database\secedit.sdb
The following Warning Message is displayed:-

Give OK and the following things happen as shown in the Screenshot.
When the Command completes.....
Press the 'Retry' Button on the Copy Error Message Box (First Picture).
There won't be any Staxmem.dll error and the file get installed easily....
Wow and now my installation is complete.....
Thanks to the one who provided me a clue......

Wednesday, December 22, 2010

TELNET IN WINDOWS 7- HOW TO GET IT?

When you go to a command prompt in Windows 7 and give our way old Telnet command, oh.... it says "Telnet is not recognized as an internal or external command, operable program or batch file".
Don't worry... Telnet is not enabled in Windows 7 by default. It is very easy to bring Telnet back in action. Follow the steps....
Start Menu > Control Panel > Programs and Features
On the left side border, you will find "Turn Windows features on or off".
Click it and the folowing window appears.

Select Telnet Client (As Underlined in the picture)
Press OK.
A Progress Bar that shows the configuration appears and completes itself.
Now close everything...
Go to a Command Prompt....
and
Telnet.
Ya it is there....

Saturday, November 27, 2010

COMMAND PROMPT FOR SYSTEM ADMINISTRATORS

Here I post something for the System Administrators, a set of most useful commands those can be executed from a Command Prompt.

In a Windows Server Domain, it become inevitable to make a change in certain client's Policy or update the Group Policy of a single PC. Administrators always prefer the Snap-in management Method... but here let's do it in old school method.
TO ACCESS THE POLICY SNAP IN OF REMOTE PC:-
Open Command Prompt
gpedit.msc /gpcomputer:
Here you may address the PC either by its IP Address or by its Domain Name
for example-
gpedit.msc /gpcomputer: 192.168.1.75
OR
gpedit.msc /gpcomputer: adminspc

The Group Policy Snap In of the specified PC opens up. You may amend as required and close the SNAP IN.

Now to make the change effective immediately-
GPUpdate /target: User /force /wait
The Wait indicates the time wait (default is 600 second) before applying the policy.
Example
GPUpdate /target: adminpc User /force /wait:2
Here wait:2 is waiting 2 seconds.

You may delve into much more- On Command Prompt, try
Gpedit /?