Search the Community
Showing results for tags 'SCCM 1606'.
Found 4 results
Hi, I have a device that is in SCCM and has multiple TS deployed to it. Although when i try to PXE the machine it aborts as it cant find any advertisements. I've checked the SMSPXE.log file and it see's that its trying to PXE but has no advertisements deployed to the device. Any help would be great!
Hello, I have recently encountered extremely slow download of the Image.wim files while in PXE environment. I have verified that IIS is not being limited and in monitoring the switch port the server is connected to I have getting on between 8-10% utilization of the 1GB port and the Server Resource monitoring is showing a max network at 100Mbps. The Image.wim file is 8.2GB and is taking roughly 6-7 hours to download. This is not a question about TFTP transfer of the Boot.wim and have in placed the Reg change to increase the block size. I have verified IIS default site has no limit on transfer. Client BITS settings are not enabled on Default Client settings. Current Environment of Distribution Point Virtual Server running on ESXi 6.0 Windows Server 2012 R2 Standard OS SCCM 1606 Distribution Point Role 8.0 GB RAM Virtual Server running on ESXi 6.0 VMXNET3 Ethernet Adapter: Speed 10.Gbps, Driver version: 126.96.36.199 VMware tools version 10.0.0.3.000743 I have attached an SMSTS,log which verifies the proper Distribution Point is being contacted for the content. This log shows the Image.WIM download starting at 10:22 AM and the Apply Operating System not starting until 5:05PM. This may be a VMware/Server issue, but wanted to verify this could not be related to SCCM prior to sending this issue up the ladder. If anything other information is needed please let me know, I have been searching the internet and I am leaning towards the VMXNET3 adapter and VM tools upgrade. Thanks for any help. smsts DP.log
Hi there, Recently we upgraded from SCCM 2012 to 1606 Current Branch. Most clients are updated successfully. I have some of them that are Failed. As show here: However, when I look at the details, it's hard to understand why. The correct client version should be: 5.00.8412.1307 In this screenshot you can see some clients that have the Failed status. Client Version Reported From DDR has the correct version. Client Version Reported From FSP/MP has the wrong ersion. Many of the clients in that list both have wrong version and all of them have a different reason for the failure. Some of those are: 0x80072ee7,Unknown Error (-2147012889) - Failed to download file over WINHTTP at address. 0x80004005,Unspecified error - Invalid ccmsetup command line. 0x80200065,Unknown Error (-2145386395) - Failed to download files through BITS at address. 0x80004005,Unspecified error - Failed to find an available source. 0x00000000,Success - Cannot install prerequisite file 0x00000000,Success - Failed to find an available source. And so on... How to tackle these issues? What is your experience with client upgrades? I don't use Client Push... I've let CM deploy the new version automatically after the upgrade.
Hello - I am in need of a little help, I have packages that are stuck in progress and will not complete. If I check the content status all I get is details will be available after the server finishes processing the messages. Any insight would be greatly appreciated. Thanks, Mike