jskfan
asked on
The Boot Image is Not Currently Available on the Selected Distribution Point
The Boot Image is Not Currently Available on the Selected Distribution Point
I have ran Task Sequence media wizard, I got to the step where I selected the Boot Image and the Distribution Point, when I clicked Next I got the message The Boot Image is Not Currently Available on the Selected Distribution Point
However If I go to the Properties of the Distribution Point and click on Content tab I see the Boot Image there.
Any idea why I am getting that error ?
Thank you
I have ran Task Sequence media wizard, I got to the step where I selected the Boot Image and the Distribution Point, when I clicked Next I got the message The Boot Image is Not Currently Available on the Selected Distribution Point
However If I go to the Properties of the Distribution Point and click on Content tab I see the Boot Image there.
Any idea why I am getting that error ?
Thank you
Can you ping the distribution point from the PC? maybe it maybe a networking issue and the computer cant communicate with the DP
ASKER
All Roles are in the same SCCM Server.
the default Boot Images come with SCCM
They are distributed to DP.
The Reference computer is able to ping the SCCM Server and vice-versa.
C:\Users\user>ping -a 192.168.254.129
Pinging SCCM [192.168.254.129] with 32 bytes of data:
Reply from 192.168.254.129: bytes=32 time<1ms TTL=128
Reply from 192.168.254.129: bytes=32 time<1ms TTL=128
Reply from 192.168.254.129: bytes=32 time=1ms TTL=128
Reply from 192.168.254.129: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.254.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
the default Boot Images come with SCCM
They are distributed to DP.
The Reference computer is able to ping the SCCM Server and vice-versa.
C:\Users\user>ping -a 192.168.254.129
Pinging SCCM [192.168.254.129] with 32 bytes of data:
Reply from 192.168.254.129: bytes=32 time<1ms TTL=128
Reply from 192.168.254.129: bytes=32 time<1ms TTL=128
Reply from 192.168.254.129: bytes=32 time=1ms TTL=128
Reply from 192.168.254.129: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.254.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
OK - I warned you it was a guess :). That's the most common mistake by far.
I also mis-read your post. This is not even booting is it. This is at the task-sequence wizard stage!
Check the box shown on the boot image. For the wizard CM needs to access the share on occasions. The error message is correct but rather misleading.
I also mis-read your post. This is not even booting is it. This is at the task-sequence wizard stage!
Check the box shown on the boot image. For the wizard CM needs to access the share on occasions. The error message is correct but rather misleading.
ASKER
Hi,
I attached a screenshot with my previous answer but it did not upload after all that!
Regardless, yes the new screenshot shows it is probably not the reason: you have distributed the boot images but it's failed, so you haven't distributed anything in fact.
Given the boot images are on the SAME machine is the path to the file OK? i.e. go to Properties of the boot image and find the path then check the file is IN that path.
Once done, look at the distmgr.log log file. Check for errors. The probable cause is this: ERROR DPConnection::ConnectWMI() – Failed to connect to (servername). error = 0x8004100e SMS_DISTRIBUTION_MANAGER
In which case you need to install another IIS role as shown here:
http://www.santhoshdurgam.com/2013/03/package-copy-failure-distribution.html
Whilst there please double-check ALL the roles SCCM needs are enabled (as per that screenshot).
SCCM is VERY unforgiving of bad setups. You will make mistakes in the beginning because setup is fiddly and everybody makes mistakes the first few times they install it. Yes, several times later it will be nearly there!! I realise you're learning but check and double-check things to make sure everything i is dotted and t is crossed.
Mike
I attached a screenshot with my previous answer but it did not upload after all that!
Regardless, yes the new screenshot shows it is probably not the reason: you have distributed the boot images but it's failed, so you haven't distributed anything in fact.
Given the boot images are on the SAME machine is the path to the file OK? i.e. go to Properties of the boot image and find the path then check the file is IN that path.
Once done, look at the distmgr.log log file. Check for errors. The probable cause is this: ERROR DPConnection::ConnectWMI()
In which case you need to install another IIS role as shown here:
http://www.santhoshdurgam.com/2013/03/package-copy-failure-distribution.html
Whilst there please double-check ALL the roles SCCM needs are enabled (as per that screenshot).
SCCM is VERY unforgiving of bad setups. You will make mistakes in the beginning because setup is fiddly and everybody makes mistakes the first few times they install it. Yes, several times later it will be nearly there!! I realise you're learning but check and double-check things to make sure everything i is dotted and t is crossed.
Mike
ASKER
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you very much!!!
I will check that when I get back to SCCM Lab
I will check that when I get back to SCCM Lab
At a pure (educated) guess, you have only distributed ONE boot image, e.g the 64-bit one. As I mentioned previously, you always need BOTH. This is by design. Distribute both boot images. Always.
Mike