Rambler

Hi. Is there a way to set a VLAN on a network adapter in WinPE (3.0/3.1)? I've found this document dealing with 802.1x auth in WinPE, but that deals with user authentication (TLS) - http://blogs.technet.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-03-31-62-58/Windows-7-Deployment-Procedures-in-802-1X-Wired-Networks.pdf I have a server with a network adapter in a tagged VLAN, therefore I need to set up the VLAN directly in the network adapter in order for it to be able to communicate in given network from WinPE. How can this be achieved? Thanks in advance

I don't know about disk management console allowing this, but you can monitor this via script - http://www.microsoft.com/technet/scriptcen...s/stdvvb10.mspx I guess you could improve it by using WMI monitoring. As for your second question - the only way I know is to enable auditing object access on the FS.

Thanks Innocent Devil, now on to testing

I'm not sure there's such tweak, but you can use the ToggleQL utility to switch quicklaunch on/off - ToggleQL

Unfortunately it's not there. There are only logos for Windows Tablet PC Edition, Freestyle edition and Server Appliance edition. I must admit I've never heard about those last two. Anyway, any more ideas? I'm not too keen on going through all those 1280 DLL files present in system32 folder :/

Hello everyone. I was asked to modify logon screen of one of the terminal servers to include company logo (replacing the windows logo). So, I modified msgina.dll, where I replaced the bitmaps accordingly and it all works fine on a Windows 2003 Server. But it doesn't work on a Windows 2003 R2 Server - I didn't notice at first, but the Windows R2 logo isn't even included in msgina.dll, but yet it's still used. My modification didn't work (apparently), because I've replaced the Windows 2003 (non-R2) logos. Does anyone have an idea where R2 server takes this logo from?

The last backslash is in wrong position. Do I get a cookie now?

It's semi-colon ";" in regfiles. Ofcourse a roughly 5s search on Google would reveal that information to you too without asking here. Edit: cluberti beat me to it

Does the login script contain anything else besides the drive mapping? If so, does it work? You might want to try to add some simple debugging info like echoing the command and output to some file or just echo something to a file to see if the file is even parsed.

I assume you are talking about the Windows command interpreter aka "cmd" - are you aware of the fact that it supports name completion? IMHO that's even faster than typing usually Not that I have anything against short names - the ones including space(s) can really sometimes be annoying.

Yes, it works despite ref.chm saying there are no entries under [Networking] section.

Here's a basic article on editing boot.ini - http://support.microsoft.com/?kbid=289022 and here's little more detailed one - http://msdn.microsoft.com/library/en-us/De...675dc22.xml.asp

Deleted. I was still half asleep when writing that reply. Oh well, let's try again. As you are not specifying any parameters after the /qn switch, it should IMO be like this: REG ADD %KEY%\010 /V 1 /D "%PP%Java\jre-1_5_0_06-windows-i586-p.exe /s /v\"/qn\"" /f

Sorry, I didn't realize you are installing from CD - that way you can't use the unattand.udb file - it can only be used when you initiate the installation manually (for example booting to dos/bartpe/winpe and using winnt.exe). But if you were installing from network distribution or started the installation manually via one of the methods, then you could use it. Simply put you add /udf parameter to winnt.exe command so it looks like: winnt /unattend:z:\unattend.txt /udf:PC01,unattend.udb when installing PC with the name PC01. z:\unattend.txt is the path to the answer file (just other name for winnt.sif) and unattend.udb is the Uniqness Database File - the values from it overwrite the values in the answer file. So let's illustrate on my little example - I have this unattend.udb file: ;SetupMgrTag [UniqueIds] PC-01=UserData PC-02=UserData PC-03=UserData [PC-01:UserData] ComputerName = PC-01 [PC-02:UserData] ComputerName = PC-02 [PC-03:UserData] ComputerName = PC-03 Now when I want to install PC with the name PC-03, I use this command: winnt /unattend:z:\unattend.txt /udf:PC-03,unattend.udb This way you can have as many predefined names as you want. You can ofcourse override other settings of the answer file in the .udb file, but just be warned that inserting Windows product key never worked for me this way (although it is supposed to). Sorry for bit offtopic comment. PS: I think you have to use winnt32.exe instead of winnt.exe when installing from WinPE (and I assume the same goes for BartPE).

Um, why don't you just use unattend.udb file with all the names of those computers - you apparently know them ahead, so that would be easy to implement.

I was testing this recently (had a font collision with one app) - at one point I deleted all the .ttf fonts. After rebooting Windows worked just fine - it also recreated some of those .ttf automatically. I can't give you the list though, as I've not written it down. But it's a simple enough test to perform.

http://support.microsoft.com/kb/319974 Btw, it's also the first link google returns (along with ton of other relevant links).

While true for CD install, for network install, it looks in the i386 for the $OEM$ folder by default, but you can specify other location by using the OemFilesPath entry under the [unattended] section.

What exactly are you asking for?

Actually no - at least there's not much info in HKLM\Software\OpenOffice.org and there's no OO key in HKCU. But I did little more thorough search and found that all user specific settings are in "%appdata%\OpenOffice.org2". You can backup/copy back this folder, but you need to quit OO and OO quicklaunch before or else the settings will remain in memory/cache/somewhere. Maybe this bit of info will be useful to someone besides me. This is true for OO2.0, can't confirm for 1.x versions atm. Note: actually, when you delete "%appdata%\OpenOffice.org2", you will get the welcome screen again when you launch OO.

Does anyone know where OO2.0 stores application settings? In OO1.4, I simply copied the whole share and user folders for simplicity's sake and it worked fine. I'm wondering if the same approach would work in OO2.0 or if it's possible to use some better technique?

Um, this is what public betatesting is about - you don't release a test build and then issue patches to it. Instead you fix the errors and release next build (in this case beta2 (besides the other leaked builds)).

julianmay - as far as i know, you can't logon automatically with domain credentials - the only way to automatically logon after installation is with the local (machine) administrator (which you specified in winnt.sif) via using AutoLogon=Yes, AutoLogonCount=1. Don't forget if you use these, you must use unencrypted password in winnt.sif

Windows setup automatically looks for winnt.sif on floppy, so you just put it on floppy and have it in the fdd when the installation starts.

Nor can I. Haven't seen this before. <{POST_SNAPBACK}> As it is not part of unattend.txt/winnt.sif, but winbom.ini, which is used in factory mode. But that doesn't mean it won't work in unattend.txt - maybe it's silently supported, have someone tested it? And as for diskpart - yes, windows setup uses it to do the partitioning.