Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Everything posted by jackinv

  1. Yeah I've thought about using other softwares to sidestep it. I guess really what it comes down to is don't log into your account locally if you're going to log into it remotely later. And if you do decide to log into it remotely later, don't press log off or log off locally before logging in and out remotely at a later time. This hopefully won't be an issue when I'm gone because I'm the only one with access to that user anyhow.
  2. I've reduced this issue to being that if I start my computer, and log into my account at the user selection screen then regardless of whether I select "switch user" and leave the account on or leave the account on the desktop then RDP into it then disconnect it will show my desktop to everyone. However... it seems that if I start the computer and use RDP FIRST to log onto the account then disconnect it will kick back to the user selection screen. I then got to wondering, ok, what if I login on the remote computer first, then RDP into it, then disconnect, then reconnect and finally select log off. This of course gives me the dreaded "Maximum Connections" problem. And supposedly I should be able to log in with my administrator account via mstsc /console (RDP console) but this ALSO does not work. Regardless if I try to use my user account (which has admin privledges) or the hidden Administrator account that I set and pass up for. Either way it still gives me the "Maximum connections" problem. I've used the following in Command prompt: mstsc /v:SERVERNAME /f -console (where servername is ip or name), mstsc /console, and mstsc /admin. None of these worked :\ Any one have a solution to either of these problems.
  3. There's probly and easy solution to this one but I can seem to string the right words together to find my desired answer. I'm trying to remote connect into my home XP machine from my XP/Win7 laptop(I have the same issue either way). Now remote desktop works perfectly but when I disconnect either from the start menu or by clicking the X the remote computer flickers then goes to the user account I was working on and stays on, meaning whoever wants to mess with my account can. Obviously not something I want. Is there a way to disconnect and have the remote computer kicked to the user switch screen but stay logged on. Meaning that someone could click on that account and have to put in the pass or be forced to use a different account where as I if I wanted to could just remote back into it at another time? Thanks.
  4. Hm well before you got back to me I just tested it, I had done the previous removal of Pending.XML then went into vlite and selected the Component Cache component. It seemed to install fine using VMWare not going through method 2. Dunno if it have remained stable, I didn't really try to do anything with it besides seeing if it would install and open a few windows.
  5. Alright, so I put on the vlite "extreme" trigger I just need to remove the Component Cache (WinSxS) component and I'm good to go? or something breaks and I bug you about it... but I've got the directions correct now right?
  6. Am I reading this correctly? I just need to mount the wim, delete Pending.XML, commit and unmount then make a bootable disk in vlite? I did that and my Winsxs came out to be something like 1.75gb the same as it was before I deleted Pending.XML :|
  7. I'll try that out. I got sidetracked for a moment. I decided I couldn't rip Win7 down enough so decided to install XP Tablet Edition for my new Tablet PC and then realized either due to XP itself or some driver issue it's TERRIBLE compared to Windows 7 in regards to pressure sensitivity accuracy. So now I'm back to square one. Anyhow another problem. I know how to go about adding and removing packages in dism. At least the basic packages. But how to I end up and remove packages like Hyper V, Business Scanning etc?
  8. You have to delete files both in file respiratory and Winsxs to recover space. First u need to take ownership of both file respiratory and winsxs folder ownership. Then delete prn for printers,wia for Camera and mdm for modem related entries from both folders.In winsxs it is prefixed with x86 for ex x86prn. Very good, I found most of the stuff I was looking for. But I've tried taking ownership, and it supposedly says it is successful yet still gives me the "You require permission from TrustedInstaller to make changes to this folder" and thus can't delete anything. Who is this trustedinstaller? And how do I kill him? edit: I first did the take owner ship through a context menu registry hack, I did it through Command Prompt this time and now it says that "You require permission from (my pc's name that just took ownership) to make changes to this folder. This seems like a problem with me perhaps trying to edit within VMWare perhaps? Is it impossible for the virtual machine to take ownership?
  9. Hey guys, I've been working trying to Lite my Windows 7 Installation for the past few days with a lot of trial and error (just like everyone else I'm sure) Anyhow, I've got it to where it'll pretty much install with everything I need but now I'm trying to get over the hump of removing Printer, Camera and Modem drivers in WinSxS and DriverStoreFileRepository from a mounted image. But I haven't exactly found how nor what exactly I'm supposed to delete. I'm guessing that since I'm trying to get it off the image itself I should be dealing with the .Wim file in dism. Any clues about how to go about doing this? Or is a better method to find all dupe files in WinSxS and delete them?

  • Create New...