Hi Guys,
I have experianced a strange behavior with a different HDD to chage for on of my Clients. The first (built-in) HDD (SSD) was identified every time without any Problems. Now i´ve a different SSD which replaces the allready built-in SSD.
Whene i want to install Windows 7 x64 via tasksequence by my SCCM2012, the SCCM runs in a problem because it wasn´t able to locate a propper disk to install.
Whene i open a command prompt via F8 in PXE, there is no disk to select in "Notepad-View (X:\Notepad.exe -> Computer)". I used Diskpart with the following Options:
1. Diskpart
2. List Disk (i can see the 250GB SSD)
3. List Volume (there is no volume on disk)
4. create Partition Primary (on the selected disk (HDD))
5. select Partition 1
6. Format fs=ntfs quick
Now i was able to see a volume on the disk, as expected.
7. assign (only for me to see that it also works with "Notepad -> Computer")
After a reboot and pressing F12 for PXE Boot, SCCM sucessfull starts to deploy the machine without any Problems. The SSD, which i built in, is a testing device from OCZ. Whene it´s working, we want to order some more for our Notebooks.
So i don´t have a second disk for more testing. A second "OSD" on the existing disk works.
Now, lets go further to the question.... is it possible that SCCM expects a certain configuration of the disk which is used for installation?
Many thanks in advance and sorry for grammer mistakes, i´m not a native speaker :-).
Kind regards, Rob