Nizam Mohamed

Uncategorized

Desktop Boards — Keyboard prompts during boot process POST

Here’s this list for function keys during POST for Intel boards.

During the boot-up process, before the operating system loads, you can press certain Function keys and Control key combinations to launch different tasks.

Function key or Control key Purpose
F2 Accesses the BIOS Setup program.
F7 Initiates a BIOS update process where the update files are stored on a USB thumb drive. For instructions on this BIOS update method, seeInstructions for F7 BIOS Flash update.
F8 Opens the Windows* boot option menu which allows you to boot into safe mode, enable boot logging, perform restore tasks, and more.
F9 Launches the Remote PC Assist Wizard. This function is only available when the board supports Intel® Remote PC Assist Technology (Intel® RPAT).
F10 Accesses the boot menu and displays all bootable devices to select from.
F12 Allows you to boot to a network; generally used to install an operating system from an image on the network.
Control-I Opens the Intel® Rapid Storage Technology option ROM user interface.  This prompt is available on boards that are configured for and support RAID.
Control-M Opens the Marvell RAID option ROM user interface. This prompt is available on boards that are configured for and support Marvell RAID.
Control-P Opens the Intel® Management Engine (MEBx) Configuration user interface. This prompt is only available on certain boards that support the Intel® Management Engine.

Desktop Boards — Keyboard prompts during boot process POST.

Uncategorized

Windows could not complete the installation (after sysprep).

This got me going again…
New Member
Join Date: Feb 2011
Posts: 1
Thanked: 0
      02-09-2011
Here’s what I did to solve it for myself (I had run sysprep /generalize /oobe to move my machine from an AMD to an Intel platform):
1) Get the command prompt with Shift-F10.
2) Run services.msc and turn anything that you disabled yourself to Automatic (use your head here, for example Nero’s NMIndexService can stay off), in case you’ve done services tweaking like I did.
3) Ensure the sptd service is disabled if you have it installed (used for virtual CD/ISO-mounting apps), you do this with regedit, it’ll be in HKLMSystemCurrentControlSetServices I believe.
4) Reboot
5) Command prompt again, cd to WindowsSystem32oobe and run msoobe
6) Create a new user and go through the steps.
After the OOBE part was done, I just got a black screen instead of going to desktop. Just sat there, so I powered off and rebooted. After reboot, it logged me into the new user I had created.
7) Log back into your old user, all should be fine now.
Hope this helps someone out there.
Reply With Quote

New Member
Join Date: Feb 2011
Posts: 1
Thanked: 0
      02-24-2011
Thanks Gypsy. I tweaked your post a bit and did the following:
After getting the command prompt:
I ran MMC > Add Remove Snap In > Computer Management > System Tools > Users to change my Administrator password to meet the requirements.
Then
Add Remove Snap In >Group Policy Object > Local Computer >Computer Configuration > Windows Settings>Security Settings>Local Policies>Security Option and changed “Accounts: Administrator Accounts status” to enabled. From there a restart and “bob’s your uncle”!
Uncategorized

How to dynamically create security-enhanced redirected folders by using folder redirection in Windows 2000 and in Windows Server 2003

In Microsoft Windows 2000 and in Microsoft Windows Server 2003, as an administrator, you can customize desktops by using Folder Redirection. You can redirect the following folders by using Active Directory and Group Policy:

  • Application Data
  • Desktop
  • My Documents
  • My Documents/My Pictures
  • Start Menu

You can find more information about Folder Redirection by searching Windows Help for Folder Redirection.

When you redirect folders to a shared location on a network, users need both read and write access to this location so that the users can read the contents these folders. However, in some scenarios, you may not want to grant read access.

Create security-enhanced redirected folders

To make sure that only the user and the domain administrators have permissions to open a particular redirected folder, do the following:

  1. Select a central location in your environment where you would like to store Folder Redirection, and then share this folder. In this example, FLDREDIR is used.
  2. Set Share Permissions for the Everyone group to Full Control.
  3. Use the following settings for NTFS Permissions:
    • CREATOR OWNER – Full Control (Apply onto: Subfolders and Files Only)
    • System – Full Control (Apply onto: This Folder, Subfolders and Files)
    • Domain Admins – Full Control (Apply onto: This Folder, Subfolders and Files)
    • Everyone – Create Folder/Append Data (Apply onto: This Folder Only)
    • Everyone – List Folder/Read Data (Apply onto: This Folder Only)
    • Everyone – Read Attributes (Apply onto: This Folder Only)
    • Everyone – Traverse Folder/Execute File (Apply onto: This Folder Only)
  4. Configure Folder Redirection Policy as outlined in Windows Help. Use a path similar to\serverFLDREDIRusername to create a folder under the shared folder, FLDREDIR.

Because the Everyone group has the Create Folder/Append Data right, the group members have the proper permissions to create the folder; however, the members are not able to read the data afterwards. The Username group is the name of the user that was logged on when you created the folder. Because the folder is a child of the parent folder, it inherits the permissions that you assigned to FLDREDIR. Also, because the user is creating the folder, the user gains full control of the folder because of the Creator Owner Permission setting.
How to dynamically create security-enhanced redirected folders by using folder redirection in Windows 2000 and in Windows Server 2003.

Uncategorized

Microsoft: Windows Server 2008 – recommended dns settings for domain controllers running 2008 server

 
Taken from tek-tips.com to clear up DNS server misconception.
Quote:
 

Primary is local first then any other DNS server second

 
That is actually a very common misconfiguration in DNS servers. The first DNS server listed (aka, primary) should NOT be the server itself. The correct method is to list one or more DNS servers as the primary, secondary, and on the advanced tab, and then add the loopback IP address (127.0.0.1) as the last DNS server in the list. If you run the DNS Best Practice Analyzer it will confirm this.
 
The reason is pretty simple. If you set the DNS server to use itself for DNS lookups then it will never query another DNS server unless its own DNS service isn’t running. That means that it is entirely possible for it to become isolated from the other DNS servers in your environment if it doesn’t have the appropriate records to locate the replication partners, and you’ll never know that anything is wrong until you run into name resolution issues.
Microsoft: Windows Server 2008 – recommended dns settings for domain controllers running 2008 server.

Uncategorized

Making a WinPE CD

Here’s 8 steps to create a bootable WinPE CD:

  1. start “Deployment Tools Command Prompt” as administrator
  2. copype.cmd x86 c:winpe_x86
  3. Dism /Mount-WIM /WimFile:c:winpe_x86winpe.wim /index:1 /MountDir:c:winpe_x86mount
  4. Dism /image:<path_to_image> /Add-Driver /Driver:(Here I put the folder path to the folder with the .inf and .sys files) /recurse (the /recurse causes all the drivers in that folder to be added)
  5. dism /unmount-wim /Mountdir:c:winpe_x86mount /commit
  6. copy c:winpe_x86winpe.wim c:winpe_x86ISOsourcesboot.wim
  7. oscdimg -n -bC:winpe_x86etfsboot.com C:winpe_x86ISO C:winpe_x86winpe_x86.iso (this creates a burnable .iso)
  8. Burn the .iso to CD/DVD.

via Making a WinPE CD with HP SmartArray Raid Drivers « BasementJack.