totoymola

Thanks for the tip and for the code RogueSpear! I can't wait to try it out. I'm currently enjoying my two weeks vacation (thats why I wasn't able to read monitor the posts on this thread) and I'll be working again on the 21st. Dude, I must admit that I'm a REAL noob when it comes to networking.. I don't even understand the concept of active directory!

Hey Nanaki!! This thread really deserves to be sticked! Keep it up!

I don't know whats the difference, but this is my Copy To and Move To tweak. [HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\Copy To] @="{C2FBB630-2971-11d1-A18C-00C04FD75D13}" [HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers\Move To] @="{C2FBB631-2971-11d1-A18C-00C04FD75D13}" Looks the same as the above though..

I have a few problems. 1. The shutdown is not working, and I don't know how to shutdown or restart. 2. The theme is not set automatically on the start menu, only on the taskbar. (The Start Menu is set to "classic") 3. I can't use my existing nu2menu.xml files with xpe. I always get an error message. I haven't played with the xpe-custom.inf yet, maybe the settings are there. edit: I now know the shutdown command. But I still have no idea how to change the Start Menu to "XP Style". edit2: got everything i need.

Yeah! I used the XP files for my UA. Hehehehe.. To set the theme, I used WindowBlinds. I was thinking of using Aston because it looks better, but I'm not familiar with it. And I still prefer using Explorer. About the boot time, that's a good question. I think it takes more than 3 minutes to boot.. I'm using a dvd-rw though. It should be faster on a regular cd on a regular cd drive. With WindowBlinds, I used this extra inf file to set the metallic theme. [Version] Signature= "$Windows NT$" [PEBuilder] Name="Windows Blinds XP-Metallic" Enable=1 [Default.AddReg] ; Default theme XP-metallic 0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset","\Programs\WindowBlinds\LunaXP\Metallic.SSS" 0x1,"Software\Stardock\WindowBlinds\WB5.ini\WBLiteFX","Skinset2","Windows XP Style" Again, muchas gracias!

Look here. http://www.msfn.org/board/index.php?showtopic=53287 That is my "test" build, which turned out nicely. I know UBCD4WIN, and if I'm not mistaken, you can't change the taskbar there using the method on you link. The reason (I think) is because it is using GeoShell, not Explorer. However, there is a way to change the skin of GeoShell, but I don't know how to do it. PS: I used WindowBlinds

Because of Simon's wonderful PE, I was encouraged to build mine once again. It is still a work in progress, but I'm very glad because the themes are finally working!! Here are some screenshots. One more. I'm not joking! This is a real PE built using BartPE Builder v3.1.3. Thanks Simon for inspiring me, and for mentioning the XPE plugin!

I usually edit the PEBUILDER.INF. What are the other methods?

Really nice Simon. I haven't tried the Win XPE plugin, but it looks really nice. I will try to build another one. Mine is almost one year old! Wait, do I still need the nu2menu if I'm going to use the Win XPE plugin? I really wonder how ERD Commander's theme works..

Hell yeah! I was a noob a year ago! And I'm still a noob until now.

I can't believe this. I think I have posted **** msi on three or four different threads already, but the demand is still high.. Anyway, here is another link for anyone who needs it. http://sr1.mytempdir.com/105409 Hey wutsup Nologic! I've seen J.A.N.E. almost a year ago, but I didn't use it because I don't know how to configure it. It has tons of options that I don't understand..., and I thought is is a payware because I saw a "unregisteredr" word in the about dialog box!!

msp's??????what this??/ <{POST_SNAPBACK}> Hey dude! I don't know why you want to repackage a very large MSI installer like this. Is it because: a) you want to integrate updates to the original installer? or b) you want to have a custumized installer that contains all your settings, ect. ? If a, you don't have to do repackage it because you can simply integrate the msp to the original installer. MSP is the format of the update patch that the developers release if they have updates for their msi installers. If b, why not use an MST? An mst is a transform file, that contains all the settings for your custom installation. It has the same concept as the winnt.sif file for unattended installation of Windows. Repackaging an msi is not a good idea, especially for enormous softwares like Office2003! The main reason is because every msi has a unique characteristic. You will never get an exact same package. When Microsoft release an update for Office2003, it is not gonna work on your repackaged version because the update is for their original msi release only. Next, it is really difficult!! Huge installers has thousands of files and registry entries!! And just in case you don't know, msi installers create their own registry entries even if they are not related to the software. So in my opinion, your snapshot repackaging method will not do it. You are lucky to have AdminStudio, the complete software for software packaging. But you cannot just rely on the Repackager. For example, the registry entries. Repackager will most likely capture most (but DEFINITELY not all!) of the registry entries created by the msi installer. But like I said earlier, not all those entries are related to the software. So how can you seperate the just the important entries if you have thousands of them? Seriously, that a lot of work. And even if you are successfull repackaging a working installer, it will never be 100% perfect. Hey, don't get me wrong. I'm not trying to discourage you. It's really your choice, so do whatever you want. I'm just trying to show you the disadvantages. Sheesh.. I remember when I was starting to learn.. You might also find this useful. http://www.msfn.org/board/index.php?showtopic=38802&hl= Good luck!

Rule of thumb: Never repackage an msi. That's why we have msp's. Or if you want customized installations, use mst's.

InstallShield rules!! I used it to repackage the two small softwares in my sig.

Hi. I tried searching for that program but I wasn't able to find it. Is it the same as the Acronis Snap Deploy? By the way, I use InstallShield for repackaging my softwares if I want to make an MSI installer, and Inno Setup or Setup Factory for regular exe installers.

sonic is correct. You cant do that on all types of installers. There are some that support changing the default install path, but some do not. I think the only solution for those is either by using autoit, or repackaging the software.

Hi. If it works on Google Earth, then there is no reason why it is not gonna work on the pro version. By the way, that is a new installshield switch. I don't think I've seen that before. I still don't understand why they didn't use msi for their installer..

I personally don't like the new name. But I don't really care. I'm still gonna use it anyway.

true

Hmmm.. That's odd.. Because I tried the exact same thing weeks ago without success. Anyway, I will try it again. And if its really not working, I will just try the psexec + autologon method. However, i have to manually "allow" psexec on all the computers because the anti-virus is blocking it.

Yes. You are both correct. Regedit+Remote Registry and the reg.exe from the resource kit can both modify registries remotely. But the thing is, the remote system is not using the admin account. So I can't really modify their registries..

Thank you Earthcoder and sixpack for the links. I will read and try them. Thanks for the tip. That is what I was actually thinking. However, my problem is, the limited account doesn't allow modification of registry. And the "Workstation Only" checkbox in the logon screen confuses me. Oh well.. Do you guys know of a tool that can modify the registry remotely? I purchased a software called Registry Workshop several months ago, and it can open the registry of remote computers. However, it doesn't show everything, and I can't modify the registry of the limited account.

Hehehe.. Well, just in case you're curious, it is the biggest fast food company in the Philippines. Believe it or not, McDonald's is no match when it comes to taste, and it is not even close when it comes to the average daily sales.

I have a similar problem. But mine is is a little more complicated. http://www.msfn.org/board/index.php?showto...ndpost&p=354913 Yes there is a way to shutdown those computers. Try using the Shutdown utility from Windows2000 Resource Kit or Windows XP, or Sysinternals' PsShutdown. PsShutdown v2.42 - Shutdown, logoff and power manage local and remote systems Copyright (C) 1999-2005 Mark Russinovich Sysinternals - www.sysinternals.com usage: psshutdown -s|-r|-h|-d|-k|-a|-l|-o [-f] [-c] [-t [nn|h:m]] [-e [u|p]:xx:yy] [-m "message"] [-u Username [-p password]] [-n s] [\\computer[,computer[,...]|@file] -a Abort a shutdown (only possible while countdown is in progress) -c Allow the shutdown to be aborted by the interactive user -d Suspend the computer -e Shutdown reason code (available on Windows XP and higher). Specify 'u' for unplanned and 'p' for planned shutdown reason codes. xx is the major reason code (must be less than 256) yy is the minor reason code (must be less than 65536) -f Forces running applications to close -h Hibernate the computer -k Poweroff the computer (reboot if poweroff is not supported) -l Lock the computer -m Message to display to logged on users -n Specifies timeout in seconds connecting to remote computers -o Logoff the console user -p Specifies optional password for user name. If you omit this you will be prompted to enter a hidden password. -r Reboot after shutdown -s Shutdown without poweroff -t Specifies countdown in seconds until shutdown (default is 20) or the time of shutdown (in 24 hour notation) -u Specifies optional user name for login to remote computer. computer Shutdown the computer or computers specified @file Shutdown the computers listed in the file specified Reasons defined on this computer (U = unplanned, P = planned): Type Major Minor Title U 0 0 Other (Unplanned) P 0 0 Other (Planned) U 1 1 Hardware: Maintenance (Unplanned) P 1 1 Hardware: Maintenance (Planned) U 1 2 Hardware: Installation (Unplanned) P 1 2 Hardware: Installation (Planned) U 2 3 Operating System: Upgrade (Unplanned) P 2 3 Operating System: Upgrade (Planned) U 2 4 Operating System: Reconfiguration (Unplanned) P 2 4 Operating System: Reconfiguration (Planned) U 4 1 Application: Maintenance (Unplanned) P 4 1 Application: Maintenance (Planned) U 4 5 Application: Unresponsive U 4 6 Application: Unstable

Still waiting..