Jump to content


sccmrookie

Established Members
  • Posts

    21
  • Joined

  • Last visited

sccmrookie's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. thanks kman - just wondering the best way within sccm config man - but appreciate gpo maybe able to do what i want. thanks
  2. Hi I have managed to find the fault - however to my knowledge where I was having the problem you can't invoke the F8 command - only during the task sequence in win p.e can you do this. The problem was to do with the custom settings file - .xml for the operating system. I removed that and the build works fine, back to 35 mins now including applications. As alternative to the .xml file i recaptured the .wim file with local settings applied and this has worked fine. thanks all
  3. Hi just a quick questoin what is the best practice for achieving the following 1.) ensuring machine has local firewall disabled 2.) remote desktop enabled 3.) uk keyboard/local configured 4.) extra local admin account So it is best to capture the above from a workstation and use in a base/golden image/wim file? Or... create individual task sequences for the above? I've figured out how to do uk keyboard and extra local admin account so far steps in t.s, but just wondering what is best practice Thanks all.
  4. Hi After months of headaches and being side tracked i've now got sccm osd via offline usb 99% there ! Prior to me adding in some small apps (citrix receiver plus 2 other small ones), and an additoinal local admin account and keyboard localised uk settings it's now gone on the go slow. So before the fine tuning 30 mins to install win7 via usb 3.0 stick, "out of the box install". now 1 hour 30 mins.. Citrix receiver manually takes 5 mins max, and surely configuring an extra local admin account and keyboard local would take 5 mins real time plus trend anti virus about 5-10 mins max? So 30 mins to 1 hours 30 mins?? The setup takes an extra 30 /40 minutes at this stage now - "setup will continue after restarting your computer" it literally sits here for ages ! All drivers everything works though... Thoughts?
  5. True. All users should be informed before a machine is rebuilt. But users in a corporate enviroment should never store data locally. All docs and settings should be on network drive.
  6. If you password protect the task sequence surely that will then not need this caveat thrown in? e.g if you put in the task sequence password you know your about to wipe the machine !! if you don't put in the correct password nothings going to happen?? simples... or am i wrong?
  7. The op is only asking for real world examples of how many machines can be rebuilt simulateneously... fair question - is it documented anywhere how many clients in the "real world" can be rebuilt at one time?? Has anyone ever been brave enough to initiate huge rebuilds across a live infrastructure/network?? has it been "perfect" ?? My dealings with configmanager 2012 have been frustrating to say the least. I unfortunately have to now get to grips with configmanager for osd (forced too) , I've spoken with some real world top SCCM experts and apparantly 30 mins for an image with a lite build is good/average. I personally prefer blasting machines with clonezilla or acronis..5 mins vs 30 mins?? - But it is what is ...
  8. Hi fred/everyone sorry not posted sooner now fixed !!! I got this solved ! and working 2 things needed to be adjusted. 1.) diskpart and clean disk into the task sequence then another error message was thrown up and stopped the task sequence which I will post up asap. (different error code) problem 2 stopping it working machine was booting usb stick from uefi - not legacy... but booted into the task sequence and the failed.. Changed it to legacy mode in boot mode pre task sequence and it is now working ! I will find the full task sequence and let everyone know as this really has been a mission. Thanks everyone and sorry for not updating sooner.
  9. Hi Fred . what do you think of the error code? Am I in the right ballpark ? Still don t understand as it partition s and format s desktops fine. Also if I have manually Deleted the partitions prior to imaging via USB stick don t understand why cleaning the partitions would help ??
  10. Hi Fred . what do you think of the error code? Am I in the right ballpark ? Still don t understand as it partition s and format s desktops fine. Also if I have manually Deleted the partitions prior to imaging via USB stick don t understand why cleaning the partitions would help ??
  11. further searching around brings me this Maybe the partitioning is set wrong??, although it worked for the laptops https://4sysops.com/archives/sccm-windows-deployment-troubleshooting-part-2-disk-related-issues/ according to this guy, the parameter is incorrect. Error 0×80070057 CAUSE: no C: volume exists FIX: Open a shell and use diskpart to create a C drive
  12. Hi I have found someone else who had the same issue but i have applied their fix - OSDisk instead of System variable under the formatting task sequence and it still doesn't work.They have also had the same error code as me. The /target parameter specifies an invalid target location. Failed to run the action: Apply Operating System Image. The parameter is incorrect. (Error: 80070057; Source: Windows) http://www.deploymentresearch.com/Research/tabid/62/EntryId/53/Troubleshooting-tips-Refreshing-clients-with-SCCM-2012-and-MDT-2012-RC1.aspx Still not fixed this, I can also confirm that UEFI is not the problem in the bios /smart boot, and the hard drive has also been freshly formatted. I've tried this on both hp pro desk 400g1 and hp pro desk 600 g1. ??
  13. PXE = wds issues to my limited knowledge. I would uninstall and reinstall wds service and see what happens. Also check all services are running that are relevant - dhcp. next question. Have you got a machine added to the domain that can ping the sccm config manager server and can you ping from the sccm config manager back to the same machine? Not an expert but these are the things I would do /check 1st in my very limited knowledge of sccm.
  14. hi found what fixed my pxe issues http://www.windows-noob.com/forums/index.php?/topic/9368-wds-service-crashing-not-starting-sccm-2012-r2/ I applied hotfix kb2910552 . This may/may not help but i thought worth mentioning.
  15. Hi Fred, here's the log file, now it is huge so I will post the first paragraph and the last2 paragraphs... don't know if i can post entire log.txt files/attach them here? <![LOG[LOGGING: Finalize process ID set to 836]LOG]!><time="14:46:43.885+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="tslogging.cpp:1495"> <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="14:46:43.885+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:1055"> <![LOG[succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="14:46:43.885+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="util.cpp:964"> <![LOG[Debug shell is enabled]LOG]!><time="14:46:43.885+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:1066"> <![LOG[Waiting for PNP initialization...]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:60"> <![LOG[RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="configpath.cpp:302"> <![LOG[WinPE boot path: D:\SOURCES\BOOT.WIM]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="configpath.cpp:327"> <![LOG[booted from removable device]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="configpath.cpp:357"> <![LOG[Found config path D:\]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:548"> <![LOG[booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="14:46:43.901+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:582"> <![LOG[D:\WinPE does not exist.]LOG]!><time="14:46:44.151+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:599"> <![LOG[D:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="14:46:44.151+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:613"> <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="14:46:44.151+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:860"> <![LOG[The command completed successfully.]LOG]!><time="14:46:51.225+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:942"> <![LOG[starting DNS client service.]LOG]!><time="14:46:51.225+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:666"> <![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:D:\]LOG]!><time="14:46:51.731+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:860"> <![LOG[The command completed successfully.]LOG]!><time="14:46:51.731+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="844" file="bootshell.cpp:942"> <![LOG[==============================[ TSMBootStrap.exe ]===" Last 2 paragraphs where it fails "omponent="TSManager" context="" type="1" thread="756" file="instruction.cxx:751"> <![LOG[Expand a string: WinPE]LOG]!><time="14:47:46.820+480" date="10-29-2014" component="TSManager" context="" type="0" thread="756" file="executionenv.cxx:782"> <![LOG[Executing command line: OSDApplyOS.exe /image:01000035,%OSDImageIndex% /target:%system% /runfromnet:False]LOG]!><time="14:47:46.820+480" date="10-29-2014" component="TSManager" context="" type="1" thread="756" file="commandline.cpp:827"> <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="ApplyOperatingSystem" context="" type="0" thread="1100" file="commandline.cpp:228"> <![LOG[set command line: "OSDApplyOS.exe" /image:01000035,2 /target:%system% /runfromnet:False]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="ApplyOperatingSystem" context="" type="0" thread="1100" file="commandline.cpp:731"> <![LOG[((g_Target.Disk > 0) || (arg == L"0")) && (g_Target.Partition >= c_MinPartition), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,254)]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="ApplyOperatingSystem" context="" type="0" thread="1100" file="applyos.cpp:254"> <![LOG[The /target parameter specifies an invalid target location.]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="ApplyOperatingSystem" context="" type="3" thread="1100" file="applyos.cpp:254"> <![LOG[ParseCommandLine(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,429)]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="ApplyOperatingSystem" context="" type="0" thread="1100" file="applyos.cpp:429"> <![LOG[Process completed with exit code 2147942487]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="1" thread="756" file="commandline.cpp:1123"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="1" thread="756" file="instruction.cxx:804"> <![LOG[Failed to run the action: Apply Operating System. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="3" thread="756" file="instruction.cxx:895"> <![LOG[Do not send status message in full media case]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="1" thread="756" file="utils.cpp:5763"> <![LOG[set a global environment variable _SMSTSLastActionRetCode=-2147024809]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="0" thread="756" file="executionenv.cxx:668"> <![LOG[set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="0" thread="756" file="executionenv.cxx:668"> <![LOG[Clear local default environment]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="0" thread="756" file="executionenv.cxx:807"> <![LOG[Let the parent group (Install Operating System) decides whether to continue execution]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="0" thread="756" file="instruction.cxx:1004"> <![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)]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="3" thread="756" file="instruction.cxx:217"> <![LOG[Failed to run the last action: Apply Operating System. Execution of task sequence failed. The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="3" thread="756" file="engine.cxx:213"> <![LOG[Do not send status message in full media case]LOG]!><time="14:47:46.836+480" date="10-29-2014" component="TSManager" context="" type="1" thread="756" file="utils.cpp:5763"> <![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="14:47:54.766+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:860"> <![LOG[The command completed successfully.]LOG]!><time="14:47:54.766+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:942"> <![LOG[successfully launched command shell.]LOG]!><time="14:47:54.766+480" date="10-29-2014" component="TSBootShell" context="" type="1" thread="840" file="bootshell.cpp:432"> " So edited bulletpoints again - The usb stick works for HP Laptops - hp 4530 and hp4540 aswell and installs some packages aswell. – not all of the drivers install but the majority work It will not work with a hp prodesk 400g1 or hp prodesk 600 g1. This is to deploy windows 7 64 bit. The pxe environment works, and so does the capturing a reference machine via network also too. Niall I will work through these exercises asap ... do appreciate the input. CM12 in a lab - Part 17. Using MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 18. Deploying a UDI Client Task Sequence
×
×
  • Create New...