Bishop

I was indeed able to solve the problem by using your firewall rules and importing them on my laptop and PC. Both work fine now and they both have the Remote Desktop item showing up in the application list. Thanks for solving that problem. Let's hope this get's fixed in a possible future version. Thanks Glimmerman.

For some reason the PC I installed with RT7Lite have the above 'bug'. It comes forward since I am unable to connect to any of my RT7Lite installs using Remote Desktop. I've searched google and this forum and my best guess is this. I indeed have the above stuff missing. How would I create such a rule? I have tried creating a program rule that points to: C:\Windows\System32\mstsc.exe and then allowing the connection. That didn't solve the problem. But perhaps I'm creating the wrong rule.

Hmmm, makes me wondering. Anyways, it will need some research. I will try to find out later and respond to you. Yes all sucessfull drivers are added to MountDir\Windows\System32\DriverStore\FileRepository Folders will be in cryptic type like if I had my NVidia driver captured with Driver Magician and the .inf name was oem14.inf then it creates a Folder called oem14.inf_amd64_neutral_a54ca838cecfddb2 in the Windows\System32\DriverStore\FileRepository thats for 64 flavor also, all mine go the the System32 location Hell yeah, this is exactly what I ment. The only problem now is how to identify the drivers. Thanks for your input guys.

Well the window shows wether theyre integrated successfully or not, for example it says that a driver or more failed to be integrated and i can just scroll up. True true,.. but I was away when my PC was processing. I got back and it said: Done! So.. is there a log I could check? Perhaps I'm looking in the wrong location.

Perhaps one of the more obvious questions but I have no clue... Is there a way to confirm if the drivers you tried to integrate are actually integrated? For example when testing the built image with VirtualBox can I also 'see' if the drivers I intended to integrate are actually present?

I'm right over here. ;-) I'm just not that experienced with Windows 7, and the stuff needed to integrate things. I've done so on XP with nLite, and for Vista I used vLite. That's all the experience I've got so far. I'm currently experimenting with both 7customizer and Win Integrator. Both look very promising! I've had some problems with getting the unattended bit to work, but I fear it's something really obvious so I hold untill I absolutely have no other idea's left. I'm watching... but you might not see me... ;-)

Grabben, remove your key m8.

My guess is that you are trying to use an image that is located in a folder with spaces. Eg: D:\Windows 7 x64 Professional, instead you should make sure the folder has no spaces. In this case: D:\Windows_7_x64_Professional.

So... I've come across "dism exitcode'8' I don't have the experience or the know-how to find what the problem is. I suspect Win Integrator's last action is the one that causes the error? In that case "KB974065" is doing something. I have searched for the exitcode here and in the rest of the forum but I can't find any reference. I've posted my log below. Any idea's? Cheers. WinIntegrator.2010_01_20T22_56_17.txt