[mssms] Windows 10 1703 Start Menu Problem

[Johns, Damon (DoJ)]

Hi Everyone,

This is a little off topic however a colleague of mine is having a problem with 
his Windows 10 1703 deployment and the start menu.

He's posted to the Microsoft forums here:

https://social.technet.microsoft.com/Forums/en-US/f59ec1ce-005d-4339-b5b2-b49044ee9aed/problem-with-windows-10-1703-start-menu-using-group-policy?forum=win10itprosetup

If anyone can offer some suggestions or assistance he would be very 
appreciative.

Cheers
Damon



CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.

RE: [mssms] RE: Problems imaging a Surface Studio

[Jason Sandys]

For now maybe. Not supported doesn’t necessarily mean it won’t work, just that 
they neither design nor test against the item not supported and thus YMMV. 
Doing unsupported things leads to unsupported results.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Mike Murray
Sent: Thursday, July 20, 2017 3:38 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] RE: Problems imaging a Surface Studio

We’re able to image all of our other models with Win10, no issue.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: Thursday, July 20, 2017 12:46 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] RE: Problems imaging a Surface Studio

That is correct. Only limited support of Windows 10 1511 and LTSB 2015 is 
provided by ConfigMgr 2012. No support for any other version of Win 10. That 
may or may not explicitly be the problem here, but it is a problem nonetheless.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Adam Juelich
Sent: Thursday, July 20, 2017 10:53 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Problems imaging a Surface Studio

Does that version of ConfigMgr even support deploying Windows 10?  I thought it 
only supported managing Windows 10 with Software & Updates?

On Thu, Jul 20, 2017 at 8:30 AM, Jerousek, Jeff 
> wrote:
We’ve built one recently without any extra storage drivers.

I would try a “diskpart; select disk #; clean”, first.

Thanks,
Jeff Jerousek


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 5:37 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Problems imaging a Surface Studio

I’m assuming we need to import that storage driver for it, can anyone confirm?

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Problems imaging a Surface Studio

We got our first Surface Studio (with a 2TB drive) and have been having trouble 
imaging it (CM2012 R2 SP1, CU4). It’s pretty unresponsive over the wire, and 
then bombs out with this error in the SMSTS.log:

The execution of the group (Install Operating System) has failed and the 
execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 
7/19/2017 11:38:49 AM 1916 (0x077C)
Failed to run the last action: Run AppSelector. Execution of task sequence 
failed.
The request could not be performed because of an I/O device error. (Error: 
8007045D; Source: Windows)TSManager 7/19/2017 11:38:49 
AM 1916 (0x077C)

This seems to be a disk corruption type error.

We tried again with standalone media and it blue screened with “stop code 
NTFS_FILE_SYSTEM”.

Are there any special steps we need to take to image these?


Best Regards,

Mike Murray
Desktop Engineer/IT Consultant - IT Support Services
California State University, Chico
530.898.4357
mmur...@csuchico.edu

Remember, Chico State will NEVER ask you for your password via email!
For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

[mssms] RE: Error updating boot image

[Jason Sandys]

The driver may or may not be old. The problem is that driver injection into 
boot images comes from the original location that you imported the drivers from 
and **not** the package source location. Many folks mistakenly delete the files 
they originally imported the drivers from thinking that they are no longer 
needed and thus essentially shoot themselves in the foot. You only recourse 
here is to restore the drivers exactly as they were in the locations noted or 
to remove the drivers from the boot image.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Mike Murray
Sent: Thursday, July 20, 2017 7:03 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Error updating boot image

CM2012 R2 SP1 CU4. When I try to import drivers and update the boot image, I 
get this error:

[cid:image001.png@01D30199.9F178860]

I tried attaching the dism.log file, but it's too large. I believe the relevant 
stuff is below. It looks to me like it's trying to find an old driver that no 
longer exists on the server. Not sure what I can do about this, but I need to 
update my boot image. Help!

[cid:image002.png@01D30199.9F178860]


Best Regards,

Mike Murray
Desktop Engineer/IT Consultant - IT Support Services
California State University, Chico
530.898.4357
mmur...@csuchico.edu

Remember, Chico State will NEVER ask you for your password via email!
For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

Re: [mssms] SCCM server moving to different Box-- need help

[Kevin Ray]

can any one explain back difference between sccm maintenance task backup
and Studio management SQL Backup...which is one Good ?

and am looking my Task sequence to restore. any document which items we
can restore from  daily maintenance task backup

On Thu, Jul 20, 2017 at 12:07 PM, Kevin Ray  wrote:

> Hi All,
>
> Due to some issues on my SCCM server( Windows server 2012 & SQL 2016)... I
> have to move different box.. I have the daily SCCM back with me..
>
>
>
> My plan is : For new box I'm thinking to Plan same IP and Same server name
>
> then I will install the SCCM on new box then I will restore the Daily sync
> backup...
>
>
> what is the Best approach and any suggestions please?
>
> And what kind of information i will get from SCCM daily back(which is
> maintance backup)
>
>
>
>
>
>
>
>

[mssms] Error updating boot image

[Mike Murray]

CM2012 R2 SP1 CU4. When I try to import drivers and update the boot image, I
get this error:

 



 

I tried attaching the dism.log file, but it's too large. I believe the
relevant stuff is below. It looks to me like it's trying to find an old
driver that no longer exists on the server. Not sure what I can do about
this, but I need to update my boot image. Help!

 



 

 

Best Regards,

 

Mike Murray

Desktop Engineer/IT Consultant - IT Support Services

California State University, Chico

530.898.4357
  mmur...@csuchico.edu

 

Remember, Chico State will NEVER ask you for your password via email!  

For more information about recognizing phishing scam emails go to:
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

 





smime.p7s
Description: S/MIME cryptographic signature

[mssms] RE: Windows 10 OSD 'Failed to install boot image' from Software Center

[Dave West]

To answer your question, yes, but in all honesty I'm don't remember working on 
this issue myself.  We stopped work on this issue last year to concentrate on 
our Windows 7 service, but in the past few months we have been working on the 
Windows 10 service again and we don't have this issue.

Looking at our task sequence, at the beginning we set a variable 
OSDBitLockerStatus=Protected using WMI:
WMI Namespace: root\cimv2\Security\MicrosoftVolumeEncryption
WQL Query: select * from win32_encryptablevolume where driveletter = 'c:' and 
protectionstatus = '1'
Then we use the built-in 'Disable BitLocker' step if 
OSDBitLockerStatus=Protected.
Then we restart in Windows PE:

[cid:image002.png@01D301A7.D5532AC0]

The rest of the task sequence is fairly standard after that.

I would surmise that this allows BitLocker to be disabled in Windows and allows 
the boot image to be staged before rebooting to WinPE.

Sorry I'm a bit cagey with my answer, the original issue was some time ago and 
to be honest I had forgotten we had that issue at all.  We have had consultants 
in helping us work on the new Windows 10 service and either they, or one of my 
colleagues, must have added this.

Let me know if this helps.

Dave

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Daniel Ratliff
Sent: 19 July 2017 16:16
To: mdt...@lists.myitforum.com; mssms@lists.myitforum.com
Subject: [MDT-OSD] RE: Windows 10 OSD 'Failed to install boot image' from 
Software Center

Dave, did you ever find the root cause here? We just ran into the same issue 
last night on a machine.

Daniel Ratliff

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West
Sent: Wednesday, November 23, 2016 5:08 PM
To: mssms@lists.myitforum.com; 
mdt...@lists.myitforum.com
Subject: [MDT-OSD] RE: Windows 10 OSD 'Failed to install boot image' from 
Software Center

As this is a test build I'm only running the built-in Windows Defender, no 
other Anti-Virus is installed.

I get your point about access denied being the cause. Initially I thought it 
might be BitLocker, but the 'disable BitLocker' step in the task sequence 
completes successfully.

It seems that the key is the line 'Failed to copy Z:\EFI\Microsoft\Boot\BCD...' 
which then leads to the ultimate failure of 'BootLoader::restore: 
C:\_SmsTsWinPE, Z:\...' as  I don't think it is mounting the BCD to Z: 
properly, if at all.

I don't know anything about the specific process that is used so I just don't 
know how to diagnose it any further :(

Dave

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys
Sent: 23 November 2016 17:58
To: mssms@lists.myitforum.com; 
mdt...@lists.myitforum.com
Subject: [mssms] RE: Windows 10 OSD 'Failed to install boot image' from 
Software Center

0x80004005 does not equal "Access Denied".

File in use is often indicative of anti-virus scanning a file and then locking 
it.

J

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Feret, Greg
Sent: Wednesday, November 23, 2016 9:21 AM
To: mdt...@lists.myitforum.com; 
mssms@lists.myitforum.com
Subject: [mssms] RE: Windows 10 OSD 'Failed to install boot image' from 
Software Center

Task sequence execution failed with error code 80004005 Equals access denied.

I would say you are having trouble writing to the disk for some reason.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Dave West
Sent: Wednesday, November 23, 2016 7:06 AM
To: mssms@lists.myitforum.com; 
mdt...@lists.myitforum.com
Subject: [MDT-OSD] Windows 10 OSD 'Failed to install boot image' from Software 
Center

Hi all,

We are having an issue here with our Windows 10 image in that if we try and 
initiate an OSD from Windows via Software Center the task sequence fails with 
'Task sequence execution failed with error code 80004005' but if us PXE it 
works fine.

An extract from the log seems to indicate there is a problem staging the boot 
image...

Backing up existing boot system.
BackupEfiBoot: Z:\, C:\_SMSTaskSequence\backup-EFI
Failed to copy Z:\EFI\Microsoft\Boot\BCD to 
C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD. 0x80070020
Failed to copy Z:\EFI\Microsoft\Boot\BCD.LOG to 
C:\_SMSTaskSequence\backup-EFI\EFI\Microsoft\Boot\BCD.LOG. 0x80070020
BcdBackup: C:\_SMSTaskSequence\BCD-EFI\bcd
Executing command line: "bcdedit.exe" /export C:\_SMSTaskSequence\BCD-EFI\bcd
Process completed with exit code 0

[mssms] RE: Problems imaging a Surface Studio

[Mike Murray]

I'll try this. Thanks!

 

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Shane Alexander
Sent: Thursday, July 20, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Re: Problems imaging a Surface Studio

 

Not got one to confirm, looks like yes.

 

Know this is MDT link, yet Step 6 talks about storage driver.  Put it in
your Boot Image and Driver Package.

 

https://blogs.technet.microsoft.com/askcore/2017/06/14/deploy-surface-studio
-using-mdt/


 
 Deploy Surface Studio using MDT | Ask the Core Team

blogs.technet.microsoft.com

Hi, my name is Scott McArthur and I am Supportability Program Manager in
Surface. Today I am going to walk through deploying Windows 10 Enterprise
Version ...

 

 

  _  

From: listsad...@lists.myitforum.com 
 > on
behalf of Mike Murray  >
Sent: Thursday, 20 July 2017 8:36 AM
To: mssms@lists.myitforum.com  
Subject: [mssms] RE: Problems imaging a Surface Studio 

 

I'm assuming we need to import that storage driver for it, can anyone
confirm?

 

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com  
Subject: [mssms] Problems imaging a Surface Studio

 

We got our first Surface Studio (with a 2TB drive) and have been having
trouble imaging it (CM2012 R2 SP1, CU4). It's pretty unresponsive over the
wire, and then bombs out with this error in the SMSTS.log:

 

The execution of the group (Install Operating System) has failed and the
execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager
7/19/2017 11:38:49 AM 1916 (0x077C)

Failed to run the last action: Run AppSelector. Execution of task sequence
failed.

The request could not be performed because of an I/O device error. (Error:
8007045D; Source: Windows)TSManager 7/19/2017
11:38:49 AM 1916 (0x077C)

 

This seems to be a disk corruption type error.

 

We tried again with standalone media and it blue screened with "stop code
NTFS_FILE_SYSTEM".

 

Are there any special steps we need to take to image these?

 

 

Best Regards,

 

Mike Murray

Desktop Engineer/IT Consultant - IT Support Services

California State University, Chico

530.898.4357 
mmur...@csuchico.edu  

 

Remember, Chico State will NEVER ask you for your password via email!  

For more information about recognizing phishing scam emails go to:

http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

 

 

 

 





smime.p7s
Description: S/MIME cryptographic signature

RE: [mssms] RE: Problems imaging a Surface Studio

[Mike Murray]

We’re able to image all of our other models with Win10, no issue. 

 

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jason Sandys
Sent: Thursday, July 20, 2017 12:46 PM
To: mssms@lists.myitforum.com
Subject: RE: [mssms] RE: Problems imaging a Surface Studio

 

That is correct. Only limited support of Windows 10 1511 and LTSB 2015 is 
provided by ConfigMgr 2012. No support for any other version of Win 10. That 
may or may not explicitly be the problem here, but it is a problem nonetheless.

 

J

 

From: listsad...@lists.myitforum.com   
[mailto:listsad...@lists.myitforum.com] On Behalf Of Adam Juelich
Sent: Thursday, July 20, 2017 10:53 AM
To: mssms@lists.myitforum.com  
Subject: Re: [mssms] RE: Problems imaging a Surface Studio

 

Does that version of ConfigMgr even support deploying Windows 10?  I thought it 
only supported managing Windows 10 with Software & Updates?

 

On Thu, Jul 20, 2017 at 8:30 AM, Jerousek, Jeff  > wrote:

We’ve built one recently without any extra storage drivers.

 

I would try a “diskpart; select disk #; clean”, first.

 

Thanks,

  Jeff Jerousek

 

 

From: listsad...@lists.myitforum.com   
[mailto:listsad...@lists.myitforum.com  
] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 5:37 PM
To: mssms@lists.myitforum.com  
Subject: [mssms] RE: Problems imaging a Surface Studio

 

I’m assuming we need to import that storage driver for it, can anyone confirm?

 

From: listsad...@lists.myitforum.com   
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com  
Subject: [mssms] Problems imaging a Surface Studio

 

We got our first Surface Studio (with a 2TB drive) and have been having trouble 
imaging it (CM2012 R2 SP1, CU4). It’s pretty unresponsive over the wire, and 
then bombs out with this error in the SMSTS.log:

 

The execution of the group (Install Operating System) has failed and the 
execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager 
7/19/2017 11:38:49 AM 1916 (0x077C)

Failed to run the last action: Run AppSelector. Execution of task sequence 
failed.

The request could not be performed because of an I/O device error. (Error: 
8007045D; Source: Windows)TSManager 7/19/2017 11:38:49 
AM 1916 (0x077C)

 

This seems to be a disk corruption type error.

 

We tried again with standalone media and it blue screened with “stop code 
NTFS_FILE_SYSTEM”.

 

Are there any special steps we need to take to image these?

 

 

Best Regards,

 

Mike Murray

Desktop Engineer/IT Consultant - IT Support Services

California State University, Chico

530.898.4357  
mmur...@csuchico.edu  

 

Remember, Chico State will NEVER ask you for your password via email!  

For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

 

 

 

 

 

 

 






smime.p7s
Description: S/MIME cryptographic signature

RE: [mssms] RE: Problems imaging a Surface Studio

[Jason Sandys]

That is correct. Only limited support of Windows 10 1511 and LTSB 2015 is 
provided by ConfigMgr 2012. No support for any other version of Win 10. That 
may or may not explicitly be the problem here, but it is a problem nonetheless.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Adam Juelich
Sent: Thursday, July 20, 2017 10:53 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Problems imaging a Surface Studio

Does that version of ConfigMgr even support deploying Windows 10?  I thought it 
only supported managing Windows 10 with Software & Updates?

On Thu, Jul 20, 2017 at 8:30 AM, Jerousek, Jeff 
> wrote:
We’ve built one recently without any extra storage drivers.

I would try a “diskpart; select disk #; clean”, first.

Thanks,
Jeff Jerousek


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 5:37 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Problems imaging a Surface Studio

I’m assuming we need to import that storage driver for it, can anyone confirm?

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Problems imaging a Surface Studio

We got our first Surface Studio (with a 2TB drive) and have been having trouble 
imaging it (CM2012 R2 SP1, CU4). It’s pretty unresponsive over the wire, and 
then bombs out with this error in the SMSTS.log:

The execution of the group (Install Operating System) has failed and the 
execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 
7/19/2017 11:38:49 AM 1916 (0x077C)
Failed to run the last action: Run AppSelector. Execution of task sequence 
failed.
The request could not be performed because of an I/O device error. (Error: 
8007045D; Source: Windows)TSManager 7/19/2017 11:38:49 
AM 1916 (0x077C)

This seems to be a disk corruption type error.

We tried again with standalone media and it blue screened with “stop code 
NTFS_FILE_SYSTEM”.

Are there any special steps we need to take to image these?


Best Regards,

Mike Murray
Desktop Engineer/IT Consultant - IT Support Services
California State University, Chico
530.898.4357
mmur...@csuchico.edu

Remember, Chico State will NEVER ask you for your password via email!
For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

[mssms] RE: 1702 Express Install Files

[Andreas Hammarskjöld]

Should be fixed in the next version of ConfigMgr. Known issue.

Basically you get a BITS job for each “delta” in the patch, making it very 
slow… look at it as “free” bandwidth management! 

//A

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Fast, David D.
Sent: den 20 juli 2017 17:48
To: mssms@lists.myitforum.com
Subject: [mssms] RE: 1702 Express Install Files

Is this “bug” specific to the SCCM SUP implementation of Express Updates?  We 
recently enabled Express Updates on our WSUS server (servicing mainly W7 OS), 
and I am less than impressed on the results.  It seems that clients take longer 
to download/install updates now than they did before.

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mead, Renae (DTMB)
Sent: Thursday, July 20, 2017 9:19 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: 1702 Express Install Files

We are having issues getting Windows 10 distributed to slower sites, so we 
reached out to Microsoft, which suggested using Express updates. We turned it 
on and during testing experienced severe performance issues. It took 40 hours 
to download and install patches using Express Updates. Another machine on the 
same subnet, same DP, NOT using express updates took 15 minutes to download, 
install, and reboot. Not to mention the package grew from 4GB to 24 GB.

We reached out to Microsoft with our testing results and expressed our 
concerns; they confirmed “there was a bug that they found that causes clients 
to create numerous BITS jobs (one for each byte range for the deltas to the 
package).  Each of those jobs has it's own overhead, and latency amplifies 
that.” They did confirm the fix for express updates is in escrow for the next 
Current Branch release, which should be in the next month or so.

As others have stated Express updates are not ready for prime-time.

Thanks,
Renae Mead
DTMB IS OA Enterprise Services
mea...@michigan.gov
(517) 636-0761 Office
(517) 388-2737 Mobile

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl
Sent: Tuesday, May 16, 2017 10:11 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 Express Install Files

Is anyone using this feature in SCCM 1702? I was really looking forward to 
getting this up and running after the 1702 upgrade but I am a little 
disappointed with the results I am seeing.

I understand the initial download is larger and I am okay with that, my patch 
package jumped from 13.1GB to nearly 44GB so the 2-3X size increase was pretty 
accurate. My issue is the time that it is taking to install the cumulative 
update, it is taking almost 3+ hours on my test machines. The machines are all 
W10 1607 with the latest April update applied, everything in the log files 
(deltadownload.log) indicates all is well and they are using the express files 
to install. It just takes forever to apply the update.

Is anyone else experiencing very long install times using the express install 
files? I am going to test a 1703 machine today to see if it makes any 
difference.

Thanks
Carl



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.

[mssms] SCCM server moving to different Box-- need help

[Kevin Ray]

Hi All,

Due to some issues on my SCCM server( Windows server 2012 & SQL 2016)... I
have to move different box.. I have the daily SCCM back with me..



My plan is : For new box I'm thinking to Plan same IP and Same server name

then I will install the SCCM on new box then I will restore the Daily sync
backup...


what is the Best approach and any suggestions please?

And what kind of information i will get from SCCM daily back(which is
maintance backup)

Re: [mssms] RE: Problems imaging a Surface Studio

[Adam Juelich]

Does that version of ConfigMgr even support deploying Windows 10?  I
thought it only supported managing Windows 10 with Software & Updates?

On Thu, Jul 20, 2017 at 8:30 AM, Jerousek, Jeff 
wrote:

> We’ve built one recently without any extra storage drivers.
>
>
>
> I would try a “diskpart; select disk #; clean”, first.
>
>
>
> Thanks,
>
> Jeff Jerousek 
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Mike Murray
> *Sent:* Wednesday, July 19, 2017 5:37 PM
> *To:* mssms@lists.myitforum.com
> *Subject:* [mssms] RE: Problems imaging a Surface Studio
>
>
>
> I’m assuming we need to import that storage driver for it, can anyone
> confirm?
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com ] *On Behalf Of *Mike Murray
> *Sent:* Wednesday, July 19, 2017 2:16 PM
> *To:* mssms@lists.myitforum.com
> *Subject:* [mssms] Problems imaging a Surface Studio
>
>
>
> We got our first Surface Studio (with a 2TB drive) and have been having
> trouble imaging it (CM2012 R2 SP1, CU4). It’s pretty unresponsive over the
> wire, and then bombs out with this error in the SMSTS.log:
>
>
>
> The execution of the group (Install Operating System) has failed and the
> execution has been aborted. An action failed.
>
> Operation aborted (Error: 80004004; Source: Windows) TSManager
> 7/19/2017 11:38:49 AM 1916 (0x077C)
>
> Failed to run the last action: Run AppSelector. Execution of task sequence
> failed.
>
> The request could not be performed because of an I/O device error. (Error:
> 8007045D; Source: Windows)TSManager 7/19/2017
> 11:38:49 AM 1916 (0x077C)
>
>
>
> This seems to be a disk corruption type error.
>
>
>
> We tried again with standalone media and it blue screened with “stop code
> NTFS_FILE_SYSTEM”.
>
>
>
> Are there any special steps we need to take to image these?
>
>
>
>
>
> Best Regards,
>
>
>
> Mike Murray
>
> Desktop Engineer/IT Consultant - IT Support Services
>
> California State University, Chico
>
> 530.898.4357 <(530)%20898-4357>
> mmur...@csuchico.edu
>
>
>
> Remember, Chico State will NEVER ask you for your password via email!
>
> For more information about recognizing phishing scam emails go to:
> http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml
>
>
>
>
>
>
>
>

[mssms] RE: 1702 Express Install Files

[Fast, David D.]

Is this "bug" specific to the SCCM SUP implementation of Express Updates?  We 
recently enabled Express Updates on our WSUS server (servicing mainly W7 OS), 
and I am less than impressed on the results.  It seems that clients take longer 
to download/install updates now than they did before.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Mead, Renae (DTMB)
Sent: Thursday, July 20, 2017 9:19 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: 1702 Express Install Files

We are having issues getting Windows 10 distributed to slower sites, so we 
reached out to Microsoft, which suggested using Express updates. We turned it 
on and during testing experienced severe performance issues. It took 40 hours 
to download and install patches using Express Updates. Another machine on the 
same subnet, same DP, NOT using express updates took 15 minutes to download, 
install, and reboot. Not to mention the package grew from 4GB to 24 GB.

We reached out to Microsoft with our testing results and expressed our 
concerns; they confirmed "there was a bug that they found that causes clients 
to create numerous BITS jobs (one for each byte range for the deltas to the 
package).  Each of those jobs has it's own overhead, and latency amplifies 
that." They did confirm the fix for express updates is in escrow for the next 
Current Branch release, which should be in the next month or so.

As others have stated Express updates are not ready for prime-time.

Thanks,
Renae Mead
DTMB IS OA Enterprise Services
mea...@michigan.gov
(517) 636-0761 Office
(517) 388-2737 Mobile

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl
Sent: Tuesday, May 16, 2017 10:11 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 Express Install Files

Is anyone using this feature in SCCM 1702? I was really looking forward to 
getting this up and running after the 1702 upgrade but I am a little 
disappointed with the results I am seeing.

I understand the initial download is larger and I am okay with that, my patch 
package jumped from 13.1GB to nearly 44GB so the 2-3X size increase was pretty 
accurate. My issue is the time that it is taking to install the cumulative 
update, it is taking almost 3+ hours on my test machines. The machines are all 
W10 1607 with the latest April update applied, everything in the log files 
(deltadownload.log) indicates all is well and they are using the express files 
to install. It just takes forever to apply the update.

Is anyone else experiencing very long install times using the express install 
files? I am going to test a 1703 machine today to see if it makes any 
difference.

Thanks
Carl



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance upon this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete the material from any computer.

[mssms] Re: Problems imaging a Surface Studio

[Shane Alexander]

Not got one to confirm, looks like yes.


Know this is MDT link, yet Step 6 talks about storage driver.  Put it in your 
Boot Image and Driver Package.


https://blogs.technet.microsoft.com/askcore/2017/06/14/deploy-surface-studio-using-mdt/

Deploy Surface Studio using MDT | Ask the Core 
Team
blogs.technet.microsoft.com
Hi, my name is Scott McArthur and I am Supportability Program Manager in 
Surface. Today I am going to walk through deploying Windows 10 Enterprise 
Version ...






From: listsad...@lists.myitforum.com  on behalf 
of Mike Murray 
Sent: Thursday, 20 July 2017 8:36 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Problems imaging a Surface Studio


I’m assuming we need to import that storage driver for it, can anyone confirm?



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Problems imaging a Surface Studio



We got our first Surface Studio (with a 2TB drive) and have been having trouble 
imaging it (CM2012 R2 SP1, CU4). It’s pretty unresponsive over the wire, and 
then bombs out with this error in the SMSTS.log:



The execution of the group (Install Operating System) has failed and the 
execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager 
7/19/2017 11:38:49 AM 1916 (0x077C)

Failed to run the last action: Run AppSelector. Execution of task sequence 
failed.

The request could not be performed because of an I/O device error. (Error: 
8007045D; Source: Windows)TSManager 7/19/2017 11:38:49 
AM 1916 (0x077C)



This seems to be a disk corruption type error.



We tried again with standalone media and it blue screened with “stop code 
NTFS_FILE_SYSTEM”.



Are there any special steps we need to take to image these?





Best Regards,



Mike Murray

Desktop Engineer/IT Consultant - IT Support Services

California State University, Chico

530.898.4357[X]
mmur...@csuchico.edu



Remember, Chico State will NEVER ask you for your password via email!

For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

[mssms] RE: Problems imaging a Surface Studio

[Jerousek, Jeff]

We've built one recently without any extra storage drivers.

I would try a "diskpart; select disk #; clean", first.

Thanks,
Jeff Jerousek


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 5:37 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Problems imaging a Surface Studio

I'm assuming we need to import that storage driver for it, can anyone confirm?

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Mike Murray
Sent: Wednesday, July 19, 2017 2:16 PM
To: mssms@lists.myitforum.com
Subject: [mssms] Problems imaging a Surface Studio

We got our first Surface Studio (with a 2TB drive) and have been having trouble 
imaging it (CM2012 R2 SP1, CU4). It's pretty unresponsive over the wire, and 
then bombs out with this error in the SMSTS.log:

The execution of the group (Install Operating System) has failed and the 
execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 
7/19/2017 11:38:49 AM 1916 (0x077C)
Failed to run the last action: Run AppSelector. Execution of task sequence 
failed.
The request could not be performed because of an I/O device error. (Error: 
8007045D; Source: Windows)TSManager 7/19/2017 11:38:49 
AM 1916 (0x077C)

This seems to be a disk corruption type error.

We tried again with standalone media and it blue screened with "stop code 
NTFS_FILE_SYSTEM".

Are there any special steps we need to take to image these?


Best Regards,

Mike Murray
Desktop Engineer/IT Consultant - IT Support Services
California State University, Chico
530.898.4357
mmur...@csuchico.edu

Remember, Chico State will NEVER ask you for your password via email!
For more information about recognizing phishing scam emails go to: 
http://www.csuchico.edu/isec/basics/spam-and-phishing.shtml

[mssms] Application Install Failed - Interrupting Task Sequence

[Chace Alldredge]

Not sure why this is happen, since I updated SCCM to 1702.

When Applications are included, some install - many do not and causes the Task 
Sequence to reboot and then boot into windows - not continuing the rest of the 
Task Sequence.

I removed the Application installs and it completes the image, bitlockers the 
drive. Can't seem to resolve this issue.
I checked the Network Account Settings - the service account exists and has the 
necessary privileges.
These applications all worked fine prior to 1702 - so the configuration is 
correct and they are allowed in the Task Sequence. I triple checked that.

TS environment is not initialized;
TS environment is not initialized;
TS environment is not initialized;
The system cannot find the file specified.;
Failed to run the action: Delete Folder if exists. The system cannot find the 
file specified. (Error: 0002; Source: Windows);
TS environment is not initialized;
Failed to run the action: Clear BIOS Password. The session was canceled. 
(Error: 00F0; Source: Windows);
TS environment is not initialized;
Failed to run the action: Activate TPM. Unknown error (Error: 0106; Source: 
Unknown);
App install failed.;
Install application action failed: 'Microsoft Office 365 (Project 2016 x86)'. 
Error Code 0x80004005;
App install failed.;
Install application action failed: 'Microsoft Office 365 (Visio 2016 x86)'. 
Error Code 0x80004005;
App install failed.;
Install application action failed: 'Microsoft Office 365 (ProPlus 2016 x86)'. 
Error Code 0x80004005;
App install failed.;
Install application action failed: 'Sophos Endpoint Client'. Error Code 
0x80004005;
App install failed.;
Install application action failed: 'Adobe Flash Player 26 ActiveX 26.0.0.126'. 
Error Code 0x80004005;
App install failed.;
Install application action failed: 'FileZilla FTP Client 3.22.2.2'. Error Code 
0x80004005;
App install failed.;
Install application action failed: 'Adobe Acrobat Reader DC 15.020.20039'. 
Error Code 0x80004005;
App install failed.;
Install applica! tion action failed: 'Adobe_CCPackage'. Error Code 0x80004005;
App install failed.;
Install application action failed: 'PLSQL Developer'. Error Code 0x80004005;
CreateProcess failed. Code(0x80070002);

Thanks All

[mssms] RE: 1702 Express Install Files

[Mead, Renae (DTMB)]

We are having issues getting Windows 10 distributed to slower sites, so we 
reached out to Microsoft, which suggested using Express updates. We turned it 
on and during testing experienced severe performance issues. It took 40 hours 
to download and install patches using Express Updates. Another machine on the 
same subnet, same DP, NOT using express updates took 15 minutes to download, 
install, and reboot. Not to mention the package grew from 4GB to 24 GB.

We reached out to Microsoft with our testing results and expressed our 
concerns; they confirmed "there was a bug that they found that causes clients 
to create numerous BITS jobs (one for each byte range for the deltas to the 
package).  Each of those jobs has it's own overhead, and latency amplifies 
that." They did confirm the fix for express updates is in escrow for the next 
Current Branch release, which should be in the next month or so.

As others have stated Express updates are not ready for prime-time.

Thanks,
Renae Mead
DTMB IS OA Enterprise Services
mea...@michigan.gov
(517) 636-0761 Office
(517) 388-2737 Mobile

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Enley, Carl
Sent: Tuesday, May 16, 2017 10:11 AM
To: mssms@lists.myitforum.com
Subject: [mssms] 1702 Express Install Files

Is anyone using this feature in SCCM 1702? I was really looking forward to 
getting this up and running after the 1702 upgrade but I am a little 
disappointed with the results I am seeing.

I understand the initial download is larger and I am okay with that, my patch 
package jumped from 13.1GB to nearly 44GB so the 2-3X size increase was pretty 
accurate. My issue is the time that it is taking to install the cumulative 
update, it is taking almost 3+ hours on my test machines. The machines are all 
W10 1607 with the latest April update applied, everything in the log files 
(deltadownload.log) indicates all is well and they are using the express files 
to install. It just takes forever to apply the update.

Is anyone else experiencing very long install times using the express install 
files? I am going to test a 1703 machine today to see if it makes any 
difference.

Thanks
Carl

[mssms] RE: SCCM 2012 MP in Untrusted Domain

[Jason Sandys]

The connection account enables the MP to communicate with the site’s DB so it 
should be a domain account in the same domain as the SQL server hosting the 
site’s DB. ConfigMgr should grant the proper permissions to the account 
specified in the console automatically.

Side question, why? Is there a firewall or some other network restriction 
between the members of that untrusted domain that you will be managing and your 
main infrastructure or are they perhaps remote?

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Boseman, Marcia H - Raleigh, NC
Sent: Wednesday, July 19, 2017 8:30 PM
To: mssms@lists.myitforum.com
Subject: [mssms] SCCM 2012 MP in Untrusted Domain

I am setting a management point in an untrusted forest/domain.  I can get the 
MP to install but would like clarification as what account to use for the 
Management Point Connection account.   Should it be a Domain account where the 
primary resides that has SQL rights?