Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

crane_IT's Achievements


Newbie (1/14)



  1. Ok, currently, I have our Deployment Share on our regular deployment server (MDT001) and I've created a Linked Deployment Share on a network location in our Northern branch. Their x86 Linked Deployment Share boot image is working and all the information seems to be pulling from our database (MDTDB) and populating the information. However, I'm trying to set them up with a x64 boot image for doing our Engineering Workstations, but it just sits and asks for a role. It seems to be seeing it enough to know which roles are available, but it's not seeing my database that tells it which role and which applications to pull from. I thought I've copied all the bootstrap.ini settings from the x86 image that does work, but it's still not working. Can anyone tell me what I might be missing? On a bigger picture, am I using the Linked Deployment Share as it was intended? Should I create a database and store it locally on the remote server in our Northern branch, and if so, how do I do that?
  2. Kimmyel, Thanks for the reply. Are those 2 different solutions, or is it one solution? Like, you can either create a TS host, OR you can connect remotely, or are you saying you can connect remotely by creating a TS host. If so, do you have a link I can follow to do it? I appreciate the reply!
  3. Currently, we have about 7 people who will RDP into the deployment server to add PC's to the database for imaging. For the most part, this was done because an annoyingly large portion of my day was spent adding systems to the database during our PC refresh where we were imaging 15-20 systems per day. I got so busy with that, I decided to expand the access. The problem I'm seeing now is that with RDP, we can only have 3 people max logged in at once and then you have to kick someone off. As the admin. I went to great pains to show people what to do when logged in so they didn't screw things up and to NEVER, under any circumstances, kick me out. Keeping in mind that they are IT people. Anyway, lately, I've been kicked out while updating linked deployment shares and it's frustrating that I have to go back in and lose all my stuff. So, my question. Can I set something up so that they don't RDP in and they can just add PC's to the database and nothing else? Can it be done through an MMC console and if so, how?
  4. Disregard my last comment Peter. I figured out how to do it and it's done. Now I just need to keep MS Updates from rebooting my computers during "Install Applications" and I'll be set.
  5. I may have come up with my own solution, but I'm doing testing now. I added a "net stop wuauserv" command line in the task sequence before "Install Applications". I also added a "Restart Computer" after "Install Applications". The restart should allow the update service to restart.
  6. This happens to some systems and not others during Lite Touch. Once the OS is on, I have some applications scripted to run. During the 3rd or 4th application, the MS Updates windows pops up and says it's going to force the PC to reboot because of new updates, which is does and then causes the applications installing to die and I get the yellow screen at the end. Since it's supposed to be automated, no one is around all the time to see this happen. How do I supress the MS Updates from forcing the reboot after the base image is on?
  7. Peter, can you explain what you mean by that and how this is done? I'm not sure what you mean.
  8. The way I deploy systems is to use the thinnest image possible. Currently, my base image is simply the OS version off the disk and then all other settings and applications are scripted. I tried to do updates by enabling the Windows Update (Pre-Application Installation) and Windows Update (Post-Application Installation), but could never get it to work because someone else manages SCCM and I've asked to work with him on this, so we could combine efforts, but he never gets back to me. Long story....So, I started just downloading packages and injecting them into the image through MDT. However, the older the image gets, the more updates I have to download, and then some updates break the OS deployment, etc. Anyway, if you can help me with that, good, but why I'm really posting is because I want to put on Office 2007 SP3 AFTER Office 2007 is installed. Have you guys just scripted the install or how do you keep images up to date? All the research I've done points to the aforementioned parts of the Task Sequence (Windows Update (Pre-Application Installation) and Windows Update (Post-Application Installation), but like I said, I have NEVER been able to get that to work.
  9. Peter, I've tried every variation of #2 I could find and I can get it to work under my own account, but not apply to all who log in.
  10. edwin, What I do in this case is, go into my Device Manager and if I have a yellow question mark, go to Dell's site, find the driver that makes that yellow question mark go away and then add that into the driver packages as well. See if that helps.
  11. I have an issue where I want other technicians to be able to RDP into my deployment server and add computers to the MDT database I've created. It's a simple task once I show them what to do, but I feel I've gotten the deployment server pretty well setup and the day-to-day task of adding computers to the database is simple enough with some training. However, I am trying to setup the new girl to do it and everything is OK until she clicks on Databases > Computers. When I do it, I can see all the 350+ computers we have, but she sees nothing when logged in under her account. I've changed a few things, but she still can't see them. I have done this in the past for another technician, but I just can't remember what I did to make him able to see the computers. I feel it's a permission issue, but I can't seem to remember. Any help is appreciated.
  12. I just dealt with this for several days last week. Are you using a VLK, MAK or KMS key? The link below really helped me out. Read over it thoroughly and then pick which option you would like to try. I chose #2 and it worked. It has about 4 different options to try: http://blogs.technet.com/b/deploymentguys/archive/2009/03/30/deploying-windows-7-vl-with-mak-multiple-access-keys-using-mdt-2010.aspx
  13. I agree with thadkew. I had this same issue and it's almost always been the fact that I didn't have the right NIC drivers for the hardware. Try that using DISM and see if it helps.
  14. I am working on getting USMT to work to go from an XP machine to a Windows 7 machine. I created a "Standard Client Replace Task Sequence" and updated the deployment share. I boot to the XP machine and then browse to my deploymentshare\scripts and kick off LiteTouch.vbs. I watch where the transfer file is created and it does about 9.2GB then goes to "Capture Groups" and then to "Apply Windows PE"...and this is where I have problems. I get the error message below: The logical drive could not be determined from the disk and partition FAILURE (7713): 1: Could not Determine Partition to deploy to Litetouch deployment failed, Return Code = -2147467259 0x80004005 Below this are a bunch more "Failed to run the action:" items, but I think they're probably all caused by the original failure. From the research I've done, I think it has something to do with the small diagnostic partition on this Dell D630. I went into the LTIApply.vbs and modified it by hardcoding the "DestinationLogicalDrive" to C: so hopefully it skips over the diagnostic partition. I posted on here to see if anyone else has had to deal with this and what they've done to get around it. I talked to the guy who setup our old deployment server and he recalls modifying some of the scripts, but he doesn't remember details. Any help is apprecaited.
  15. I got 3. working. cacls "C:\Program Files\...\folder" /e /grant everyone:F. I thought I had already tried that, but I guess not.
  • Create New...