maddocks1993

Brilliant. Absolutely brilliant. The last part is 110% accurate as . Good old SLT

Or just keep trying and re-installing the product numerous times as you aren't actually harming anything via imaging etc. Keep looking around for guides , videos on youtube (they have a lot) or do a course on MVA (Microsoft Virtual Academy) if they still have SCCM on there.

Hi, I would follow this guide for a starting point about SCCM, mainly to do with the SQL Process but it is very simple when you have installed it once - https://www.windows-noob.com/forums/topic/13368-how-can-i-install-system-center-configuration-manager-current-branch/ You don't have to create that amount of users nor install WSUS as a pre-Req, SCCM won't show as Failed it will show as a Warning but again Windows Deployment Services and Windows Server Updates Service integrates with SCCM. Chris.

Not certain if the Standard Edition will update SQL Express, I would be inclined to actually get rid of the SQL Express and let SCCM carry out the SQL Express as part of the SCCM installation. Chris.

I have SCCM in a virtual Machine running on 4GB Max with SQL installed tis perfectly fine! SCCM Current Branch should work completely fine on Server 2012 R2. It is down to the SQL Server. Member to change SQL Server Collation as well before installing the actual database, you don't need the entire SQL Features for the installation, you only need Database and Reporting Features plus the Management Studio. Chris.

Helloo, As Norphy said the SQL Memory allocation is just a warning and you can change that in the SQL Management Studio once SQL Server has been installed. I would recommend SQL Server 2012 with SP2 and get the latest Cumulative Updates for SQL or use SQL Server 2014. A basic Standard SQL Edition will be fine for the job. Have you also configured the SQL Server Configuration Manager Ports and added them to the Firewall? Please provide the error code. Chris.

Hello, I would highly recommend Veeam Backup & Replication with Veeam ONE - Comes under the Veeam Availability Suite. You know what Veeam can do but Veeam is the best Backup solution out there today and they will be the best for some time. You will only need to purchase license for HyperVisors, per processor but it is about 4-10k depending on what version you want from Veeam. Renewals are likely to be £300-2k depending how many years of Support you get. If you are worried about Host breaking then you can install Veeam EndPoint Backup which you can integrate into Veeam Backup & Replication console. However make sure to exclude your ClusterStorage and anything with Hyper-V as Veeam Backup & Replication will take control of the Backups in regards to your Virtual Machines. You can also Replicate to another Hyper-V Host and Backup Copy of your Backups, azure cloud connect and DR Recovery. Lot of options my friend, lot of options. Not only that, but the Instant Recovery / Replication is just brilliant and works like a treat. You can install Backup Free Edition elsewhere and do backups to a winzip file via a Powershell command. At the moment, if our Hosts break we will just set up the host completely again if not improve the host from last configuration. The hosts are just to serve RAM / Processor Power and Hyper-V. Long as your Virtual Machines are in HA mode being backed up however many times you should be fine. Regards, Chris.

Hi Nokix, Your best bet is to remove the PXE Boot from the Distribution Settings. Uninstall WDS - Restart - Install WDS Manually then Enable PXE in Distribution Settings in SCCM. I have also got this TechNet website as well. https://social.technet.microsoft.com/Forums/en-US/dd13bf24-0f66-426e-9b47-f10eb1b69841/sccm-2012-enabling-pxe-support-does-not-install-wds-on-server?forum=configmanagerosd Regards, Chris.

Hi Dr Cheese, I believe there is no best practice in order creating numerous Volumes on a SAN, reason being is because it is down to yourself or whoever will be setting the volumes up. It is mainly to do with your backup, sometimes if they Volume has been configured as one LUN then the backup may take longer, it may not. Same goes with Hyper-V, as long as you can find Storage for Hyper-V whether it's iSCSI / SMB / Fibre Channel it will be fine. You could NIC team the nodes and put an extra switch in LCAP or use the new SMB 3.0 Application Share for Hyper-V (Microsoft Recommends Now) and I have seen more people start to use SMB 3.0. Dell told us to create numerous volumes on our Tier-2 incase you wanted to replicate Volumes to another SAN. All SANs work the exact same way, so it all depends how you want to configure your SANs. As long as you have got Hot / Cold Spare disks available in the correct Raid you are fine my friend as one disk were to go down the hot spare should carry on the process whilst that broken disk gets replaced. Dell are a very 'Middle Man' I see them as, they just sell products but they rarely give you advice as they always say have you looked on Microsoft or this website. Again, they will go down the route of IOPs as well. They did that our place and told us we need this amount of IOPS when we only used a 1000 IOPS which a Raid 1 NAS could do quite easily. Keep options open as well, HP are the best for SANs / Servers. Hyper-Convergence, Nutanix (Dell & Lenovo uses Nutanix Software) , HP , Gridstore are mainly good for Hyper-V. I will give you a run down on what we have setup with our Hyper-V Cluster. 3x Nodes running Hyper-V 2x EqaulLogic via iSCSI to the 3x Nodes. 1x on a Raid10 and 1x on a Raid6 Failover Cluster installed and configured to use Virtual Machines for High Availability. Cluster Volumes are Tier-2 & Tier-3. Meaning all disks in SAN are just one Volume per EqualLogic with Correct Raid Level and Spare disks. NIC Team using LCAP or use SMB 3.0 Application with Live Migration set as SMB. We are using Veeam to backup our Virtual Machines which are done on the Hyper-V Level (Block Level). If you aren't with Veeam I would highly recommend them because the things you get with Veeam Backup & Replication is just amazing and you could restore your entire Network Infrastructure backup in a matter of minutes depending size of the Virtual Hard Disks. Chris.

Try creating the Virtual Hard Disk via PowerShell script. Just direct the Virtual Hard Disk to the C:\ of your Computer to see if you are getting the same error message as it might be Raid / Storage Path Related. You may need to specify Virtual Machine if needed. Check your Default settings in Hyper-V Manager as well as you might be creating the VHD to an old Path when a new path is available. Delete the Existing Virtual Machine and re-create then attach, you may have created a bad Virtual Machine as the VHD is not accepting it. What is your current setup with Hyper-V at the moment. Have you only got one Windows Server 2012 R2 Node in a Raid 1? How is the Hyper-V Manager laid in the Settings option? VHD Sharing will not work unless you have 2 Hyper-V Hosts in a Domain with Backend Storage available for both Hosts. At least two servers that are running Windows Server 2012 R2. The servers must be members of the same Active Directory domain. The servers must support Hyper-V. For more information, see the "Hardware requirements" section of Hyper-V overview. The servers must meet the requirements for failover clustering. For more information, see Failover Clustering Hardware Requirements and Storage Options and Validate Hardware for a Failover Cluster. The servers must have access to block-level storage, which you can add as shared storage to the physical cluster. This storage can be iSCSI, Fibre Channel, Serial Attached SCSI (SAS), or clustered storage spaces that use a set of shared SAS just-a-bunch-of-disks (JBOD) enclosures. Chris.

Hi, Yeah you can deploy a VHD or VHDX file via SCCM as long as SCCM is running with Hyper-V Enabled (Mainly a Physical box as Nested Virtualization is not out yet). Either that, run .WIM from a Task Sequence or WDS and you should be fine from there. Otherwise you will need to get the Disk Converter from Microsoft or download the Convert-WindowsImage.ps1 whether that will work I'm not certain. https://gallery.technet.microsoft.com/scriptcenter/Convert-WindowsImageps1-0fe23a8f I've converted a .wim to a .vhdx file but that was for the NanoServer which the Modules are imported from Root of Windows Server 2016 ISO. Chris.

Hi Nokix, Worse comes to worse you can uninstall the Windows Deployment Services - This shouldn't affect SCCM at all as you are only integrating WDS into SCCM and exactly the same goes for WSUS. Might be wise to delete the content of your existing directory to start from scratch. You can either install WDS via Server Manager or through the SCCM Console. I did mine through Server Manager specifying a particular path and then editing the distribution Role in SCCM. In Windows Deployment Services as well, you can set the PXE Respone as well and everything else I have left the same. I've done numerous installation's that way and all of SCCM's have been completely fine. At the moment, I am currently transferring over to SCCM Current Branch before the release of SCCM 2016 as the bosses want to go to Windows 10 this summer -.- When you upgrade to 1602, I would be inclined to check the boot image as I know Microsoft had a faulty boot image in their Assessment and Deployment Kit upon released and there was a specific hotfix to fix that issue. 1511 > 1602 is 'SCCM Current Branch'. Another question, how come you have both Virtual Machine Manager & Configuration Manager on the same box? They both can run in a Virtual Machine unless of course you have no space or SAN Regards, Chris.