SCCM broken... new install ?? needs advise

[ReadTheNetwork]

From this, it looks like your IIS is failing. Maybe a certificate is out of date or a change of password?

[techy32]

Planning to install server 2016 with SQL server 2016 ( ADK 1703 , SCCM 1702). This setup support windows 7 deployment? Windows 7 is our current environment and planning to go windows 10 with the new SCCM installation.

[Tefters]

It's easier than you think...

I'm about to do the same myself starting today.

1. Build new server with SQL and setup SCCM basics.

2. Migrate DP jobs etc...

3. Reinstate SCCM backup

 

P.S. 2nd the poster above me, you have an IIS issue there as all the components that are failing are related to IIS.

 

Presuming this isn't a VM backed up by Veeam that you can easily just re-instate a Veeam restore prior to going wrong?

Edited June 13, 2017 by Tefters

[Tefters]

Also worth checking this:

 

1 Enable Windows Authentication on IIS

2 Make sure any accounts you are using in SCCM have the right passwords.

3 Make sure there are no other websites running on port 80 or 81 in IIS.

 

In all fairness this seems like a simple fix to IIS and everything will start working again.

[techy32]

@Tefters This is not the only issue with SCCM. There are lots of other issues with it.....because someone has a very good time playing with it....

 

Can I ask if we can image window 7 with Config Manager 1702 with SQL 2016 ( with windows 10 ADK )?

[skell]

Yes sir

[Tefters]

@Tefters This is not the only issue with SCCM. There are lots of other issues with it.....because someone has a very good time playing with it....

 

Can I ask if we can image window 7 with Config Manager 1702 with SQL 2016 ( with windows 10 ADK )?

 

Yes you can, there is no mentioned from MS whatsoever of them depreciating Windows 7 support as of yet.

[techy32]

@skell Yes sir

 

I love this answer...................thank you

Edited June 13, 2017 by techy32

[ReadTheNetwork]

You can still image Windows 7 using Windows 10 boot image.

[techy32]

New SCCM is ready now... I have a question about OS deployment. Can I use the old images from my broken SCCM with new task sequence? Or I have to capture new images with the new SCCM server?

[Tefters]

Use existing images, just copy WIM's over

[techy32]

@Tefters Great. Thank you

[techy32]

Thank you everyone for your help .

 

All is setup for the new system and working fine ( Windows server 2016 with CM 1702.

 

The problem I have now is whenever we image a PC and try to re-image we have to delete the PC from SCCM. We used to re-image PCs as many time as possible without deleting the PC from SCCM and It always keeps the old name in SCCM and OU.

 

Are you doing the same thing during imaging and what about keeping the same name during re-imaging?

[Annabelle]

Which collection are you deploying the task sequence to?

 

When you first image the machines, most likely you would have deployed the task sequence to "Unknown devices".

After imaging, it is no longer "unknown" and so when you try to reimage the same machine, no task sequence will be available to it.

You then had to do what you did and that is to remove the machine from SCCM so that is it unknown to SCCM again.

Alternatively is to add the machine to another device collection and then deploy the task sequence to this new device collection that you created.

[sparkeh]

Not sure if this helps, but I have two task sequences: one targeted at the unknown computers collection and one targeted at all devices (with a password of course )

[techy32]

@Annabelle I think this was the piece which was missing

 

"Alternatively is to add the machine to another device collection and then deploy the task sequence to this new device collection that you created."

 

This way it will keep the name in SCCM and AD.

 

Thank you very much......

[ReadTheNetwork]

If it helps, I've created two AD groups for this. One group is forced and the other is advertised.

 

My membership rule for the forced deployment (forces the deployment on the machines and requires no further input).

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SecurityGroupName = "MYDOMAIN\\OS-WIN7-X64-FORCE"

Edited June 19, 2017 by ReadTheNetwork