Jump to content

n0xi3

Member
  • Posts

    11
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About n0xi3

Profile Information

  • OS
    Windows 7 x64

n0xi3's Achievements

0

Reputation

  1. Hey guys, so we have been trying to push images to both Lenovo m58p's and Dell Optiplex 980's remotely through Symantec Ghost Everytime it is done//configuring system settings we get an error message that states the Unattend file cannot be parsed at pass specialize and that the error was detected while processing settings for component[microsoft windows Unattend Join} We have tried most everything we can think of to alleviate this problem, with no luck. This happens no matter what image we push, or what type of machine we are pushing too. Anyone have any suggestions as to why we may be getting such an error? Let me know if we need to post anything. We think there might be something that *has* to be included in specialize, is this the case and maybe we left something out? What we have checked so far :: Account names and passwords Domain name is correct and properly entered It time's out giving us that error on both types of machines Old images captured before this issue, still create this error when being pushed. (thus eliminating that it may be the capturing process messing up)
  2. We have actually ran into a bigger issue, I am going to post a new thread.
  3. We tried using the tech one on friday for all of the passes but we replicated the same exact problem =( We will try some more stuff and I will update soon, but if you have more suggestions please go ahead and throw them up.
  4. Because we are on a domain setup, we use the Local Administrator account to install any specific software that is not included in our images. We really havn't found a good alternative to this. We have tried a bunch of different things.. looks like it still is not connecting to the domain anymore.
  5. Now whenever we send the image through ghost the Administrator account does not log in automatically but whenever we log it in manually, it runs sysprep and then disables the account when we try to log in after the restart.. Do we know why this may be happening we are pretty stuck. Let us know if we need to send you anything.
  6. We tried what you suggested but it got stuck trying to log into that account and would not join the domain. Which is worse then what we had. Were going to change the files back to what we were at originally since that did not work.
  7. That day you have is the date the image was originally captured from the machine. However some of the errors back then are not applicable now since our unattend files change. We are going to run a new image and see what panther says then. We will let you know what it comes up with. Hopefully it will show us errors that are happening for us to get stuck. I will go ahead and make a new post once this is done. Not sure when we will get to it though. (hopefully later today)
  8. Attached is what we came up with. I am not sure we are running the program correctly. We ran sysprep.exe and then used the cmd file afterwards and it gave us the $Panther folder with some error logs and etc. (the folder is zipped below). I am not really sure what to make out of it, or how it relates to our problem. Any suggestions from here? $Panther.zip We may need to use it when we are Imaging the computer instead of just running sysprep?
  9. Meant to be uppercase, Ill be sure to edit that. I will take a look at panther.cmd and see what it says. Might not get to this until next week though =( I will be back to update for sure. Do we need to install all of those things in order for the panther.cmd to spit out what were looking for? And are we running this where our answer file is? or on the PC we are trying to push the image to? The instructions got me kind of lost. Ill be sure to update with what we come up with.
  10. Added those changes, but problem still existed. After the System is configuring settings page it pops up with the .\Administrator login and says the password we entered was incorrect. I then proceed to login manually and it restarts and everything from there works flawless. =/
  11. Hey guys, I have managed to get our image working flawless except for one point during the windows installation. The issue is that during the setup, windows try's to login as .\Administrator. For whatever reason it gets stuck and says the password is incorrect. The password is the same as our Administrator password but we are really looking more or less to take this login or pass out of the equation in general when we are pushing images. Is this possible? Thanks for any help! **INFO We are pushing images using Ghost We are dealing with Domains, but it is connecting after the manual login This happens on both our images (Dell // Lenovo) This is our current answer file http://pastebin.com/wGCRp4SA
×
×
  • Create New...