agarabaghi

I cannot get wds / mdt 2012 to work right =( I have my network guy switch dhcp to the new server ip addess and i try to boot in. PXE says its talking to the new imaging server (imaging02) but when MDT loads it looks exactly like 2010... of course im only getting to the login screen... Can anyone help?

I actually started with a fresh formatted machine. I mounted a win pe x64 ISO to the server and created a new .wim file from the boot file...

I had the AD admin make sure the account was added on the server, i doulbe checked my bootstrap.ini file and it is indeed imaging02 and the network unc path under Mdt properties is \\IMAGING02\DeploymentShare$ any clue??

So we got it to boot, but it seems to be for some reason pulling up the old MDT stuff, and it says my credentials are wrong when I try to log in... i hate upgrading grrr

I just followed the guide... and had the network guy change the ip from the old server to the new server and im gertting this error: downloaded wdsnbp from 10.104.0.116 windows deployment services:pxe boot aborted exiting agent

what does the applygpopack=no do? im not sure i ever changed it to yes?

It downloaded then installed, but it never moved from the downloaded section to the installed section? Any ideas?

So we finally moved over to server 2012 and im in the process of install MDT 2010 on the new server. I was wondering if there is a way to copy over all the stuff i have on the MDT 2010. The 2012 server is on a new VM... is there a simple way to copy the applications task sequences and everything else ive worked so hard on?

Update 24 hours in... Red Dots appear for only 5-10 seconds on shutdown / power up and reboots (which is different from the previous 1min time it took). No red dots have remained, yet. Changes made: 1) Enabled Port Fast on Olin switch 2) Enabled IPv6 on network card settings on server 3) Re-binded all machines to AD using the Advanced bind settings from Directory Utility. Keep our fingers crossed.

Well we tried a different method of binding the machines and as of right now it only takes 5-10sec for the red dot to go away...so something is def different... Will keep updating

We have a pretty big mac pro lab. 24 machines + 1 instructor machine... All of them have the same image deployed by mac server and then each machine is manually binded to AD. When the machines turn on, it takes abour 1 - 1:30min for the red dot to go away. If it goes away everything is working. The problem is after several reboots the red dot remains. The only solution is to unbind and rebind the machines. It pretty inconsistent but they will all eventually red dot at some point of another. Im lost as to an approach, as I am not the AD admin or even sure where the issue is coming from ...

Im loading it into MDT as an application with source files, and then it ask for the command line, and im using the same one that ive been using for all my other applications. Im trying the regedt32.exe file seems liek there might be an issue with running the 64 vs 32..

and yes windows 7 sorry.

Like i said it works when you run it from the CMD prompt manually... WUserver.cmd that is... but during deployment it does not seem to want to run ...

I tried that line in the .cmd file... are you saying i should make it WUserver.bat ?

So I am having some trouble getting my MDT to deploy a registry change. I have a folder "WUserver" and i add it as an application with source files, with the command line "cmd.exe /c WUserver.cmd" There are 3 files in the folder in the Application deployment folder: regedit.exe WUserver.cmd (this is what the .cmd has in it "reg import WUserver.reg") WUserver.reg which i exported from a registry When i select that application in the list from MDT it does not make a change, but if i run the .cmd file from a command prompt it works fine. Any clues? Im going to try to change the cmd line in MDT to reg import WUserver.reg Any clues?

Ive never use WDS to take an image of a machine and deploy it. How do you deploy the image afterwards?

We are in the process of testing VMware VDI and wanted to test some of the VDI desktops in our labs. Instead of wiping the hdd on the lab machines and making them "thin" clients, i was wondering if there was a way in MDT 2010 to basically shrink the current partation ~100gigs and installed a fresh copy of windows 7 and some other software. I have been doing this manaually on some of our test machines and it works. If i could automate this and have it done to a couple machines in the lab it would serieous save some time. Any suggestions?

looks like just waiting a bit casued it to work ha.

So we are currently in a POC with this vdi technology and i seem to be running into some issues. We created a template and a base image. The base image is what we have been taking the snap shots with. Through the view web app i go to recompose the desktops pointing it to a new snap shot. The goes through the process but when i try to log into the the desktops from view it says no desktops availible. Any suggestions?

maybe i need to add the driver to the lite touch image and not just mdt?

Im having some issues imaging this computer... It's a lenovo x1 carbon and we got the USB 2.0 to ethernet adapter from lenovo. I am able to boot into the MDT2010 and click on launch deployment wizard, but it then says no networking devices were found on this machine. It's weird cause i used the adaptor to PXE boot into mdt 2010... any ideas?

So im running into an issue. If i have litetouch windows px x64 boot image mounted, everythign works fine. I can boot into MDT via Lan and install Windows 7 + all my software. We are trying to deploy Thin PC x86 via MDT now, and if i mount the x86 lite touch image, i am able to boot into the x86 version of MDT, but if there a way to select which one? I have a few techs who use the imaging server and they dont need to boot into the x86 ever. How can i make it an option?

So I am trying to remotly remove printers via a command file... rundll32 printui.dll,PrintUIEntry /dn /c\\%COMPUTERNAME% /n\\rprint01.rollins.edu\latenightlab that command seem to remove the printer, but when i go to re-add the same printer using: rundll32 printui.dll,PrintUIEntry /ga /y /c\\%COMPUTERNAME% /n\\rprint01.rollins.edu\latenightlab I get this error: Unable to add the per machine printer connection. Another printer or printer share with this name already exists. Please use another name for the printer... How do i completly delete the printer?

here is my error log: 2012/08/20 19:55:09 Starting cygwin install, version 2.774 2012/08/20 19:55:09 User has backup/restore rights 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory 2012/08/20 19:55:09 io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory 2012/08/20 19:55:09 Current Directory: c:\cygwininstall\cygwin 2012/08/20 19:55:09 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access. 2012/08/20 19:55:09 root: c:\linuxcgywin binary system 2012/08/20 19:55:09 Selected local directory: c:\cygwininstall\cygwin Found ini file - c:\cygwininstall\cygwin/setup.ini 2012/08/20 19:55:25 can't install from bad local package dir 2012/08/20 19:55:25 note: Installation incomplete. Check c:\linuxcgywin\var\log\setup.log.full for details 2012/08/20 19:55:25 Ending cygwin install