Register Now

Login

Lost Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Part 6: Configure VHDs for ConfigMgr CB Lab 2002

Part 6: Configure VHDs for ConfigMgr CB Lab 2002

In production, you will definitely use physical drives considering performance and other factors like backup and restoration. However, we will mimic production environment in our lab with the help of virtual drives. It gives you the feel and same look as production, and gives you a clear picture where specific data is stored.

Last updated 17th Feb 2020

Check-out related video to this blog post

1. Storage configuration for ConfigMgr VM

Here is the what I recommend minimum storage for different drives. If you could afford more, definitely go ahead with that.

DriveStorage NameSizeComments
C:\Local Disk50 GBOS, SQL Server Installation, ADK
D:\CM_Install40 GBConfiguration Manager Installation, MP
E:\CM_TempDB20 GBSQL Server Data Services Engine TempDB
F:\Content_Library40 GBDP, WSUS Content
G:\WSUS_Database20 GBWSUS Database
H:\CM_SQL_MDF20 GBConfigMgr Database
I:\CM_SQL_LDF20 GBConfigMgr Log Files
File ShareCM_ContentSource20 GBSource files for Applications/Packages deployment
Total250 GB

2. Configure Drives

Drive C
This drive will already be configured during OS installation on TEKNEX-CM01. No further action will be required.

Drive D
Configuration Manager and Management Point role will be installed on this drive. It will be formatted as a standard NTFS volume.

Steps to create a new VHD, attach to the Virtual Machine and format it as per the requirements.

  1. Open Hyper-V Manager > Select your ConfigMgr VM (TEKNEX-CM01 in my case) > Right-click and select Settings
  2. In the Settings Wizard select SCSI Controller > click on Add to add a hard drive
  3. Select New and this will open New Virtual Hard Disk Wizard
  4. Click Next on the Before You begin page
  5. Keep default selection dynamically expanding and select Next
  6. Specify name and location where you would like to save the virtual drive
  7. Enter size in GB and click finish

Once VHD is created and attached to the ConfigMgr VM, next thing is to format the volume.

  1. Login to ConfigMgr server and open Server Manager > Select File and Storage Services > Disks
  2. Select the drive you recently attached, which will be marked offline > right-click and click bring online > click Yes when prompted
  3. Disk will be online > select the disk and right-click > click New Volume and this will open New Volume wizard
  4. Server and Disk will be listed on the next page > click Next and select OK if prompted to bring the disk online
  5. Maximum volume size will be listed and select Next
  6. Select Drive letter (I am selecting D as I documented) for this disk and click Next
  7. On the Select file system settings page, update the following:
    – File system: NTFS (keep default)
    – Allocation unit size: Default (unless it is mentioned specifically)
    – Volume label: CM_Install (update accordingly)
  8. Click Create on the Confirmation page
  9. Open File Explorer and check the new drive

Follow the above steps mentioned to create and attach the following drives to ConfigMgr server.

Drive E
SQL Server Data Services Engine TempDB files will be saved on this drive.


Important: Microsoft recommends to format this as 64KB size (update step 7 allocation unit size while formatting this drive). Name the volume to CM_TempDB so that it can be differentiated in the File Explorer.

Drive F
Content Library will be saved on this drive and WSUS content. It will be formatted as a standard NTFS volume. Name the volume to Content_Library so that it can be differentiated in the File Explorer.

Drive G
WSUS database will be saved on this drive. It will be formatted as a standard NTFS volume. Name the volume to WSUS_Database so that it can be differentiated in the File Explorer.

Drive H
ConfigMgr database will be saved on this drive. It will be formatted as a standard NTFS volume. Name the volume to CM_SQL_MDF so that it can be differentiated in the File Explorer.

Important: Microsoft recommends to format this as 64KB size. Ensure to select 64 K Allocation Unit Size for Drive H.

Drive I
ConfigMgr database log files will be saved on this drive. Name the volume to CM_SQL_LDF so that it can be differentiated in the File Explorer.

Important: Microsoft recommends to format this as 64KB size. Ensure to select 64 K Allocation Unit Size for Drive H.

File Share

This drive will be used to save applications and packages content. It will be formatted as a standard NTFS volume. Name the volume to CM_ContentSource so that it can be differentiated in the File Explorer.

Your feedback is important to me. Leave it in the comments below 😃.

About Jay Singh


Follow Me
Subscribe
Notify of
guest
3 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Nadir
Nadir
1 year ago

Hi, I was just wondering about the purpose of CM_ContentSource. In the video, we created it as a drive on the CM server. But is this the drive you would typically want in a fileserver and share it and where you would typically keep applications, packages, drivers, driver packages and so on?

Nadir
Nadir
1 year ago
Reply to  Jay Singh

Ok perfect and thanks! I love your videos btw, I think you are doing a great job!

3
0
Would love your thoughts, please comment.x
()
x