Microsoft has made a minor change in the Disk Properties Window in Windows 10. The capacity graph has changed compared to the previous versions of Windows
Below is from Windows 8.1
Below is from Windows 10
When Microsoft released the Windows 8.1 update for Windows 8 operating systems some time back, users were able to download the and install the updated through the store. Unfortunately the below specified Windows 8 editions do not support the update from the store.
If you have a Windows 8 Enterprise and you cannot find the Windows 8.1 update in the store, download the step by step guide form the below link. To achieve this you shall require the Windows 8.1 Enterprise DVD which can be downloaded from the Microsoft Volume Licensing Service Center
Windows Update Step by Step Guide http://1drv.ms/1r86qvq
If you unplug a storage device or removable drive from your computer while it’s transferring or saving information, you might risk losing some information. In Windows you can do the following to safely remove such devices.
Another way to do this is to create a shortcut on your desktop to remove the drive. So that whenever you want remove a drive, double click on the icon, select the drive and click ok.
C:\Windows\System32\rundll32.exe shell32.dll,Control_RunDLL hotplug.dll
If you are reading this article then most probably your computer has ran out of available hard drive space in the system drive and you have tried cleaning up the drive and suddenly come a hidden file named hiberfil.sys which is huge in size and wondering if it can be deleted.
The Hiberfil.sys file is a hidden system file located in the drive where Windows is installed. Windows creates this file when the Hibernation power feature is enabled. the size of this file is approximately equal to total RAM is installed on the computer. The more the RAM the bigger the file size will be.
When the Hibernation feature is enabled in Windows and when the computer is hibernated, Windows store all the files, programs, etc. which are open to this file. In other words Windows stores a copy of the RAM to the hard disk using this file.
This file is generated only when Hibernation is enabled and when hibernation is disabled the file will be deleted and you can recover some valuable disk space.
To disable hibernation
As a safety feature and as a precaution Windows always restarts immediately when it encounters a serious/critical error (such as a blue screen stop error). This immediate restart prevents us to read/note the necessary error codes or the detailed error message that prompts on the screen to further troubleshoot to avoid similar errors in the future.
By following the below steps, one can disable the Automatic Restart to gain more time to read and note down the error messages and error codes.
The next time you receive a stop error you will have enough time to note down the error codes and the error messages which will help you to trouble shoot further
This is the final part of the 4 part deployment series
In the first 3 parts (Part 1, Part 2, Part 3) I covered on how to installing and configure Windows Deployment Services (WDS), install and configure Windows Assessment & Deployment Kit (WADK) and Microsoft Deployment Toolkit 2013 (MDT), importing operating system image to MDT, creating task sequence in MDT and finally preparing WDS for deployment.
Now that our backend infrastructure is all setup for client deployment, lets start our client and boot the machine over LAN (PXE Boot).
Press F12 for network service boot
The machine will get an IP from the DHCP and contact the WDS server
Through the WDS server the machine will provide the list of available Lite Touch Windows PE boot media’s to select from
Upon the selection of Lite Touch Windows PE, the machine will start loading the WinPE files over the network
From the Solution Accelerator screen the MDT setup will start
Click on Run the deployment wizard to install a new Operating System
Enter the admin creds and click OK
From the task sequence screen select the task sequence you created in your MDT 2013 and click next
Provide the relevant details accordingly and click next
Select do not move data option as this is a fresh installation and click next
Select do not restore user data as this is a fresh installation and click next
Provide the correct settings according to your region and click Next
Specify the local admin account password and click next
Select the necessary option for BitLocker settings and click next
Review your settings in the ready to begin section and click Begin
The installation has started
Windows is loading
Operating System Deployment is successful. click finish
Review the settings , computer automatically joined to the domain and the name is also changed
Most of the questions the Windows Deployment Wizard prompts can be disabled from MDT 2013 by customizing the deployment share rules and editing the Bootstrap.ini files. The above is the default settings.
This is the 3rd part of the 4 part deployment series.
In my first and second article I wrote on how to install and configure WDS, install and configure MDT 2013. Now that we have installed and configured MDT 2013, lets see on how to import an operating system (Windows 8.1) image to the MDT Deployment Share we created, how to create a task sequence within MDT 2013 and finally we will look at how to configure WDS to respond to client PXE boot requests.
Open the deployment workbench MMC
Right Click on the Operating Systems folder and select Import Operating Systems
On the Import Operating System Wizard select “full set of source files” and click next
Browse and select the folder where your operating system files are stored. (in this scenario I am using the Windows 8.1 DVD, hence I will select my DVD drive which is D:\) and click Next
Specify a meaningful name to the destination directory and click next
Review the summary and click next
The progress will begin
Once the progress is successful, the confirmation will display the results. click finish after reviewing
Operating System is now successfully imported
Operating system successfully added inside the DeploymentShare folder
Similarly you can add multiple operating systems (x86 and x64) according to your requirement
Upon adding your required Operating systems, applications, drivers, etc. You will need to update the Deployment Share. This process will make sure that all the latest tools and settings are copied to the deployment share. You will need to do this every time you make some changes to the image, add/remove applications within MDT 2013 so it will be updated.
To update the Deployment Share
Right Click on the MDT Deployment Share and select Update Deployment Share
In the update deployment share wizard make sure the “Optimize the boot image updating process” is selected and click next
Click next on the summary page
The progress will start
Click finish after reviewing the results in the confirmation page
The updated DeploymentShare containing the LiteTouchPE iso, WIM, and the XML files
After importing the Operating system and updating the Deployment share, you will need to configure and add the necessary WinPe (LiteTouchPE) images to WDS. This will enable you to boot your clients using PXE boot.
Open the Windows Deployment Services (WDS) mmc
Right click on boot images and select Add images
In the Add Image Wizard browse and select the location where the LiteTouchPE WIM images are stored within the DeploymentShare folder (E:\DeploymentShare\Boot) and click next
Give it a meaningful name and description. Click next
Review the setting in the summary page and click next
The image is added
Since we added only the x64 LietTouchPE.wim I will repeat the process to add the x86 wim as well so that we can deploy operating system under both platforms
Images are added in to WDS
A task sequence is a bunch of settings or instructions bundled together as a task and will be presented to be selected from the client during the deployment. Depending on the selected task sequence, the OS, Applications, settings, drivers, etc. will be deployed to the client. Basically task sequence is similar to an answer file.
Open the Deployment Workbench MMC and right lick on task sequence and select new task sequence
Provide a Unique Task Seq1uence ID, a meaningful name and a description. Click next
From the Task Sequence template dropdown, select “Standard Client Task Sequence” and click next
From the list of available Operating Systems (that are imported to MDT 2013) select the appropriate OS you want to deploy through this Task Sequence and click next
you provide the necessary values and click next (for this lab I will select the first option)
Specify the OS settings details and click next
specify the admin password (this is the password for the local administrator account and not for the domain administrator) and click next
review the summary and click next
Task sequence is created and visible in the Deployment Workbench MMC