Jump to content

cluberti

Patron
  • Posts

    11,045
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

Posts posted by cluberti

  1. I'm also no longer interested. Sinofskys replys show me that MS doesn't implement a way to disable the phone UI crap on a desktop PC by default. That's why I installed Ubuntu 11.10 and the Unity Dash has the same idea like MS with the startmenu replacement but is 1000 times better and easier to use :thumbup

    So instead of using a (pre-beta, no less) Windows interface designed for touch, you used Linux instead? I know you're a little nutty ;), but that seems like cutting off your nose to spite your face... Also, the builds everyone have access to are simply developer preview (and I'll be honest, the code quality is definitely pre-beta too), so hopefully people will at least give the OS a chance once it gets to the beta phase. Not you specifically, 'cause I know you're tied to Vista and don't like Win7 much, but I speak more generally.
  2. Unfortunately, no - I ran into this myself, and Novell confirmed that to have Win7 clients working properly without random issues (we saw network disconnections on mapped drives and logon failures), we needed to upgrade the Novell backend. Since we were migrating off of Novell onto AD in this environment, we lived with it for a few months until we were able to move everything off to the new Windows environment, and then we decommissioned the Novell environment and removed the Novell client from the client machines.

  3. When you select a task sequence, you have the option to capture it. Also, you can create task sequences simply for sysprep and capture. What you need to do is make sure that customsettings.ini and bootstrap.ini in your deployment share both have the proper UserID and UserPassword information set to allow logon - basically, map Z: to \\server\share$ using those credentials, and then browse to Z:\scripts in a cmd prompt and run cscript LiteTouch.wsf. This will realize you've already mapped Z, run LiteTouch.vbs against bootstrap.ini in the share, and show you your task sequences. Select your sysprep and capture sequence, and that should sysprep your machine, and reboot to PE to capture it via imagex to the location specified when you ran the task sequence.

  4. Yes, if you do actually want those programs, you'll need to install them. You should still add the base drivers to your installation sequence, so that you at least have video or network working when you start - then use WMI filtering or other logic to install the apps post-deploy as necessary. This is how I do it, and how many others do this as well (as you can see from Trip's post).

  5. Question

    Should I have update the deployment share after adding the new task? If so - then what option is best the first or second for creating boot wims?

    OK! The other little annoyance is the adding of the Hyper-V integration services....despite what is being said I am getting the error shown in the pic below...so what verison of Windows Server 2008 r2 do I need for that to work as it should?

    bookie32

    As to the first error, make sure you add your custom WIM like any other OS (there are guides by the Deployment Guy's blog and others how to add custom WIM files to MDT). As to the second, you shouldn't need to install the Hyper-V guest components to Windows 7 or 2008 R2 - they are already included in the driver.cab of the OS. You only need to add components to Vista and older OSes.

  6. The only real option is to get a network trace from the VM server, and make sure the boot media is indeed using the right customsettings.ini and bootstrap file contents. There's no reason for this to happen, so either the VM is getting the wrong creds, or the lookup to the DC fails.

    Again, another reason to use hyper-v ;).

  7. Hyper-V works fine, and in fact if your primary goal is to work with Windows virtual machines, you'll find Hyper-V to be better (again, assuming you don't need gigantic enterprise cluster features, full lab copy environments from production, etc - Hyper-V is "good enough" for most everything a user or SMB would need, and has the added bonus of being free, works best with Windows client OSes, and doesn't require any additional additons/etc for Windows 7 / 2008 R2 guest OSes (or higher, including Windows 8).

  8. Microsoft has never admitted any mistakes with Vista - while the driver model was a huge change with less warning than OEMs would have liked (or in fact sometimes needed), there was nothing specifically wrong with Vista as an OS. However, as with all Microsoft OSes (the professional versions at least - not the home variants), "downgrading" has always been a possibility if the OEM offered it. This would not be Microsoft's doing, however, and is only allowed if the OEM is willing to allow a customer to purchase a machine with a Vista (or Windows 7) license, and provide them also with a Windows XP license (for example).

  9. Then you're trying too hard :). In all seriousness, this works as documented in my blog, and what I did there was perhaps 200-level work (it can be even easier, just not as extendable/malleable). What specifically are you trying to achieve (at a high level), step by step? I can help, you just have to slow down, get back to basics, and allow us to help you work it out. Trust me, learning this will be *very* beneficial in the long run ;).

  10. Actually, given it is a Linux it's probably asking you if you have it to see if it can avoid loading the serial driver, and stick with the USB one (which can be loaded and unloaded without much issue, unlike the old serial bus driver). The question is actually funny if you read it as "choose one of the three, yes or no" as well if you look at it quickly without thinking too hard - which I am certainly not doing at 12:45AM ET :).

  11. All of the shutdown time here appears to be because a WMI provider takes forever to shutdown, but the CPU time is all in a thread in the shutdown logonui.exe process (showing you the shutdown status screen). To get anything useful out of this, you're going to need to take a new trace with only the following options:

    xbootmgr -trace shutdown -traceflags dispatcher+latency -stackwalk readythread+threadcreate+cswitch+profile -resultPath c:\shutdown_trace

×
×
  • Create New...