TFTP32 based RIS install
Posted 26 March 2011 - 01:19 PM
I've been using the TFTP32 based RIS install for quite some time and it worked perfectly for my scenario. I used OEM distribution share to automatically install softwares, updates and other things. The problem im facing now is that i've almost 10 different WinXP setups ranging from WinXP SP1 to SP3. In order to use OEM folders, i have to copy the same OEM folder in all 10 WinXP directories so that it can be copied during network install.
To conserve space and make my life easier, i experiment to rename the "i386" directory so that i can put all my WinXP installation in same base directory having rename their i386 folder. After some trial and error (patching setupldr.bin, editing txtsetup.sif and dosnet.inf) i was able to achieve this to some extent.
The textmode setup works fine and copies everything to hardisk but as soon as the GUI Mode setup starts, it prompt me for the location of the i386 directory. It shows me that it is searching "C:\$win_nt$.~ls\i386" while my original files are in "C:\$win_nt$.~ls\i387" directory (i have renamed i386 to i387). Now i want to fix this but im unable to find the location where it is pulling this address from.
If someone can provide any help, i shall be grateful to him.
Posted 26 March 2011 - 05:41 PM
If your server uses NTFS, you could use NTFS junctions instead of having multiple copies of the same directory. You can use Junction or LINKD to create such junction points.
...In order to use OEM folders, i have to copy the same OEM folder in all 10 WinXP directories so that it can be copied during network install.
To conserve space and make my life easier, i experiment to rename the "i386" directory so that i can put all my WinXP installation in same base directory having rename their i386 folder...
Hex-editing Windows programs such as SETUPLDR is a less pleasant approach, in my opinion.
Posted 12 August 2011 - 01:29 PM
If i use fat32 drive, i can easily setup tftpd with RIS but using ntfs causes problem. If you know how to avoid this problem pls do tell me.
Posted 12 August 2011 - 09:57 PM
Once you have formatted with NTFS, you must consider NTFS permissions and share permissions. Right-click the folders involved and choose Sharing and Security..., then you should have two tabs: Sharing (with a Permissions button) and Security. Here are my permissions:
I tried to use NTFS junctions but then another problem arises. I think ntfs doesn't allow anonymous connection to remote shares
Sharing -> Permissions button:
- ANONYMOUS LOGON: Change, Read
- Everyone: Change, Read
- Administrators: Full Control, etc.
- ANONYMOUS LOGON: Modify, Read & Execute, List Folder Contents, Read, Write
- Everyone: Modify, Read & Execute, List Folder Contents, Read, Write
- SYSTEM: Full Control, etc.
Posted 23 August 2011 - 10:57 AM
What I did was assign "Guest" user read permissions to "tftpboot" folder and allow "Anonymous Login" to tftpboot" folder from Control Panel->Administrative Tool->Local Security Policy->Security Options.
Now junctions just work as expected and im able to save disk space.
Tnx Again !
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users