Jump to content


anyweb

Root Admin
  • Posts

    9249
  • Joined

  • Last visited

  • Days Won

    369

Everything posted by anyweb

  1. you can follow the same guide and you'll see it links to a 'standalone' server installation, that's what you require (a standalone primary, no CAS), just make sure your versions of SQL match whats listed in the Part 1. Installation guide. As regards Q2, I'm not sure i've not used it, but i would do so prior to setting this up.
  2. did you try forcing the machine policy ? is the client functional ?
  3. you have the same error as before, have you looked into using /lac ?
  4. the smsts.log file will reveal why it failed to capture your image, look in c:\windows\ccm\logs\ you can post it here if you wish
  5. first things first, when you setup the SUP on your primary how did you install it ?
  6. are you using Configuration Manager 2012 or 2007 ? please raise NEW topics when you have problems instead of posting little or not info at the end of an unrelated thread.
  7. first things first, create your Windows 7 master image using the step by step guide here. Secondly post your log files so that we can see what is wrong and explain what you expected to happen and what actually happened.
  8. I have to ask, did you open loadstate.log in notepad or Trace32 ? if you did you would have seen this error (search for the word failed)
  9. look for the loadstate.log file in this location, it's listed clearly in your smsts-.... log file (did you look at the contents of that log file?) C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\loadstate.log post that loadstate.log file here and we'll help you.
  10. why did the installation fail ? can you provide the logs from the client please
  11. just make sure it's in a collection targetted with custom client settings that enable installation of the SCEP client.
  12. are you sure you followed my guides step by step, if so you wouldnt have any firewall PORT issues for sql, i can remote into your box tomorrow and take a look if you want.
  13. please raise a separate post for that question, you are mixing up two entirely different problems, it's confusing to readers. Moving this topic to Configuration Manager 2007 forums.
  14. and if you still want more content there are the videos from MMS 2012 - http://www.niallbrady.com/2012/04/23/mms-2012-videos-wouldnt-it-be-nice-to-be-able-to-download-them-all-automagically/
  15. are those file permissions set on the software folder in your screenshot, or somewhere else ? don't do a site reset, fix your permissions, are you logged on with the same account that you installed Configuration Manager with ?
  16. attach your smsts.log file from the attempt and we'll check it out, my guess is you didn't add any network drivers for your specific hardware to your boot.wim file and got no ip address which then meant the task sequence failed and it rebooted eventually to a blank harddisc or you are missing the network driver in the apply driver package step, but to be sure we need the smsts.log file, pressing F8 after enabling command prompt support in your boot images will help this.
  17. i dont see any scanstate or loadstate log files atttached above... however from the small bit of smsts.log file you posted theres the following error which means that a file (or files) are still on the hard disc (probably somewhere in the old users profile) that could not be deleted prior to applying the new os, therefore the installation failed, you'll need to examine the logs to find out what files are causing the issue.
  18. are you saying that you had permission issues on a destination share causing the error above ? if so what share (was it the capture directory ?) and what permissions did you change ? i still think based on the screenshot above that it was ip address/dns related so would like more info about your troubleshooting
  19. as Peter says, the only way to find out what is working or not with your migration is to examine the scanstate.log and loadstate.log files generated by USMT
  20. maybe you only put the drivers in one of the boot images and not the other, i'd recommend you only add the drivers you NEED to the boot images you are using, to find out which driver you need see this post please http://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/
  21. are you using a legacy network card on the virtual machine settings ?
  22. yup without a boundary and without the boundary being in a boundary group your clients cannot find their dp's, so you've solved your own problem Ben :-)
  23. how much RAM is in the machine ?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.