SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 473 | Next

Steve Seguis

"Microsoft Windows Server 2008 Administration"

exe.
Working with the registry with Windows PowerShell is easy, because PowerShell treats
the registry like a file system. If you think about it for a second, it makes sense??”after all,
the registry is organized just like a directory tree. You can think of registry keys as folders
and registry values as files. This natural similarity made it quite easy to have the registry
accessible directly through the PowerShell command prompt.
One of the most common registry keys we access is the Run key. This key stores a list of
programs to run at startup, or in the case of the Run key in HKEY_CURRENT_USER, when
the user logs in. To access the HKEY_LOCAL_MACHINE Run key from the PowerShell
console, you would run the following:
CD HKLM:
CD software\microsoft\windows\currentversion\run
Notice how this is just like going through your folder structure, except a special drive
called HKLM: takes you to the registry instead. If you want to get a list of values on
the Run key, you might be tempted to use the DIR command. If you try running this,
you might be surprised to find out that it returns nothing. The DIR command lists only
registry keys and not registry values. To get the actual registry values in the Run key,
you have to use the Get-ItemProperty cmdlet since the registry values are treated as
properties of registry keys. Get-ItemProperty requires that you specify the path of
the object for which you want to get a property.


Pages:
461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485
druga wojna światowa Free English grammar and study guid hotel jelenia góra Russian bride counter strike 1.6