dhorowitz

We have an interesting problem with our netbooks and the students' mandatory profile. I can have the same netbook and log on with a teacher account and everything logs on as expected. Periodically, a student can log in and everything is normal except for the icons on the Windows screen do not show up. There are no pop ups or bangs in event logs as to why the system didn't log on correctly. So far the only fix I have is to reboot the netbook and allow it to reauthenticate to the system. Any ideas? Desktop PCs never have had this issue.

I'm installing Windows Live Movie Maker 2011 on Windows 7 VM for use with VM-View clients. The install proceeds as normal, but when you try to launch the program, you get a message that says that Movie Maker can't start. I can't figure it out.

We use mandatory profiles...any local data is eschewed on reboot/logoff..

Anyone have a fix/hack to not show the license agreement window every time a user tries to launch this?

I'm trying to figure out how to create a USB key just with the boot information to get into the Lite Touch install provided by MDT. Everything I've found seems to want a large enough USB key to store all files and take network out of the equation which is not what I want. I just want to be able to boot the machine without having to go manually into each BIOS and reconfigure it for PXE which creates nightmares when crossing VLANs.

I've created my x86 catalog on an x86 architecture PC and updated my deployment shares with regeneration completely after creating a task sequence for x86 installation. Unfortunately when I get to the task sequence screen, it's blank. I've rebooted my server, re-updated the points. Still blank.

I'm going off of a copy of the extracted .ISO on the network. Can you tell me how to generate the 32 bit catalog using WSIM?

I haven't gotten to the point where I'm testing customizing the sysprep files. I'm just trying to import the 32 bit version of Win7 into MDT so I can start to customize my image.

Ok, I seem to have fixed the issue of the missing task sequences. Now I'm trying to make this deployment work for both x86 and x64 architectures. My MDT share is on a VM server running 2008 x64, and I have PCs that need to use the X86 version of W7. When I go to import the OS, it forces to x64. Do I need to run on server os x86 for my deployment to work properly or should I just run 2 shares?

My task sequences are not showing up on my client PC. I've set everything up using lot of default settings, and checked my permissions, everything seems like it's right. LiteTouch asks me for username/password, and that is entered fine, and the task sequence window pops up and is empty...grr.r..

I understand your input about WDS, however we don't have any WDS servers configured. Is that something that is required to do this with Windows 7?

If I remove the xml file, it runs through the sysprep no prompts for names or anything. It generates another random name. This is very frustrating.

OOPS! When it runs, the only thing it seems to do is generate a new computer name. The computer comes back to me in a usable state, however needing to re-name and manually join about 4000 PCs district wide is not going to be fun. Looking at the setup logs, I'm getting error 1355 on my attempt to join the domain which points to DNS/WINS...I can ping my DC and I can also browse the net from this machine.

false true false Eastern Standard Time true Windows 7 Product Key password administrator 1 net user administrator /active:yes name of domain domain admin password domain admin username name of domain EN-US EN-US EN-US EN-US UUFSD UUFSD false Work 1 true true true 1 That's my XML file. It runs through the sysprep process completely, no errors or bangs and reboots. I'm back where I started from. I'm using sysprep with oobe and generalize set.

I have tried installing the hotfix on my test machine and then running sysprep. After rebooting the machine, I'm experiencing the same issue with my image. It's not asking for a name or joining the domain. My workstation was never joined to the domain prior to running the Win 7 sysprep.