Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by kev_147

  1. Thanks for you comments guys, appreciated. I am not convinced though. I have WPI working with parsed commands in the example below and that doesn't state the full path. Note for Albundy33, the backslash on the end of WPI.Hta was not plain text, it was a break out within the registry command, ie informed the registry to treat everything between the 1st and 2nd \" as being within quotes. My apologies as I forgot to type in the 1st \" in my original post, have just edited it now. duh!! ******************************************************* REM ======================================== REM | This Section determines the CDROM Drive SetLocal enableextensions SET CDDRIVE=%~d0 REM========================================= REM | This Section configures the variables used within this script SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx SET ADDITIONAL_APPS=%KEY%\410 REG ADD %KEY% /V TITLE /D "Phase 4" /f REG ADD %ADDITIONAL_APPS% /VE /D "Additional Applications" /f REG ADD %ADDITIONAL_APPS% /V 1 /D "%SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30" /f EndLocal EXIT **********************************************************
  2. I have an automated build DVD and launch WPI via RunOnceEx using the following command line: %SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\$OEM$\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30 Now the above command used to work in earlier versions, but now WPI launches, but doesn't automatically set the timer to 30 seconds and choose the Corporate_Build configurations. After testing I have found that if I put the WPI folder at the root of the DVD then the following command line works: (Note: $OEM$ has been removed from the command line) %SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30 Does anyone have any ideas why this is happening? Is it happening to anyone else? I don't mind having the WPI folder at the root of the disc, but am concerned that there may be a bug in there somewhere and thought I should bring it to light.
  3. night wolf, I think I get what you are trying to do and it is something that I see the build disk at my company evolving to. Am I correct in saying that you want to choose what software/registry tweaks etc you want to apply/install right at the beginning of the Windows installation? If so, this is my idea 1. Boot off a Windows PE CD that has HTA and WSH support 2. A disk Part script launches. It would be good if a hta file could come up asking if they want to partition the drive automatically or manually. if auto, then C drive takes up whole drive, if manual, engineer enters info. 3. Drive is formatted 4. Another HTA comes up with check boxes similar to WPI, then these selections are stored within a text file on the HDD that WPI/a VBscript can read from at RunOnceEx and add the command lines to RunOnceEx process. This process would ensure that all the questions are at the start of the Windows setup, so as you say, you can answer the questions, press apply and go and have a cuppa and put your feet up. Now I know this post may be going away from WPI, but it might also be something that WPI can incorporate as the Windows PE cd can have hta support. Don't flame me guys for the above. It is just a spec of an idea in my head at the moment, any other opinions/suggestions are welcome.
  4. FAO Mark, I know you are looking at adding the ability to configure IP address, DNS, WINS, Computername. Are you also looking into the option of joing the PC to a domain. If so, can WPI give the end user the text boxes to enter username, password and domain. It would be great if this could also be hardcoded within the script for automated installs or parsed via the command line launchin WPI. Would be even better if the password could be encrypted for security reasons. Hope all is going well. Am sorry I aint really been posting much lately, am snowed under at work with a SMS 2003 project. :-) In a few weeks, will want to update my automated Win XP install to use the latest version of WPI and to also kick off the install from a Pre Installation environment, rather than th text portion of setup, but thats for another section of msfn.
  5. does this pe disc have support for WSH & HTA? Can you advise how you add $oem$ type folders to a PE disc, for example if i wanted to copy a diskpart batch file to the systemdrive
  6. Guys, can you help me out? I am sure this is a right dumb question with a simple solution, but I haven't got an idea. I want to run the following command from a logon script to install either SMS Advanced Client or Legacy Client, depending on the version of the OS: %0\..\capinst.exe /SLP="slpname"/AUTODETECT=exit1.exe The bit where it says exit1.exe is where I am having probs. I need to write a script that can return a value of 0 if the PC is Windows 95, 98 or NT4 and to return a value of 1 if Windows 2000 or XP. This script should run silently, I have seen an example of a vbscript that just has 1 line, "Wscript.Quit 1" which will make the return value to be 1. Now if this was to be written in VBScript, is there a way it can run on windows 98 machine without the need of windows scripting host, ie can it be compiled in a .exe that will work on all operating systems
  7. I couldn't see the picture. Just a bit at the top of the toolbar. Can you repost
  8. I agree with WPI being designed with a professional level in mind. For example Micro$oft see a lot of their software with about 3 different ways to do the same task. This might make things look pretty, but the code behind it must multiply and is harder to train end users. I think WPI should do exactly what it says on the tin! :-) If other ppl want pretty pictures and sounds then maybe they could have the option via a modular approach, ie enable it. But the setting should be disabled by default if not absoutlotely neccesary. Thats my 2 pennies worth. Hope it makes sense
  9. Thats similar to how we are doing it at work. I will post my final code tomorrow as I have been off work. Basically we obtain the information and write details of the laptop where the battery may need replacing and output this to a text file on a network share. We then a simple batch file to merge out that information into 1 csv file, where we can then search for make of battery first and then the model number if WMI gets this info. We found that there was a few laptops, i think the Latitude X300 where WMI didn't return anything regarding model number.
  10. Steve does that script actually get the serial number of the battery? I didn't think WMI could obtain the actual serial number of the battery, only the model number
  11. TBH I don't see the point of the Media Player. It might be a nice addition to some people, but my opinion is to leave it out by dfault and to have the media player installed in a modular way if some people wanted it. What I mean by this is to say have a configuration window whereby if you tick a box saying enable windows media player, then WPI looks at code in a java script file that just has code relevant to WMP. If the box isn't ticked then the WMP Javascript isn't used at all, can even be deleted if the person wants. Is this possible?
  12. I think the variables should match what windows outputs. Easier and read and configure. It don't look right seeing %SYSTEMDRIVE%System32 I much prefer %SYSTEMDRIVE%\System32
  13. GSH, thanks for all your help on this. I think it is a pretty neat and very useful script now. I have just incorporated it into my automated install of Windows XP.
  14. Thank You, Thank You, Thank You I thought I was going mad. It is always such a simple thing that can take ages to resolve. I was doing it within the configuration editor and didn't realise that it automatically added more back slashes.
  15. My registry at HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\DatabasePath = \\CIV-AV-01\ofcscan\FileDB It is Type REG_SZ. I have tried the following, but WPI is just greying out all 3 entries: gcond[pn]=['try{WshShell.regRead("HKEY_LOCAL_MACHINE\\SOFTWARE\\TrendMicro\\PC-cillinNTCorp\\CurrentVersion\\DatabasePath") == "\\\\CIV-AV-01\\ofcscan\\FileDB" ? true : false}catch(ex){;}']; gcond[pn]=['try{WshShell.regRead("HKEY_LOCAL_MACHINE\\SOFTWARE\\TrendMicro\\PC-cillinNTCorp\\CurrentVersion\\DatabasePath") == "\\\\MOR-AV-01\\ofcscan\\FileDB" ? true : false}catch(ex){;}']; gcond[pn]=['try{WshShell.regRead("HKEY_LOCAL_MACHINE\\SOFTWARE\\TrendMicro\\PC-cillinNTCorp\\CurrentVersion\\DatabasePath") == "\\\\SSD-AV-01\\ofcscan\\FileDB" ? true : false}catch(ex){;}']; My 3 entries in WPI are: 1. Trend - Civic 2. Trend - Moorside 3. Trend - SSD Can someone help me please? Is it something I am doing or an issue with the version of WPI I am using? The version I am using is 5.0.1 at the moment, am about to change to the latest, but need to iron out a few other issues with my automaed install 1st. Mark, help me please, this is doing my head in. Can anyone get this to work? You don't need to install the software to check, just create the registry key manually.
  16. nice one Mark, will make things easier for me and hopefully others as well.
  17. Thanks for the feedback. Especially if you aren't feeling 100%. I have just finished off restructuring the .vbs file. I have followed the same structure that GSM used in the oeminfo.ini post. All credit goes to GSM. You the Man!! I am not 100% sure what in the attached file has fixed the error with it not writing the information to file the 1st time round, so if anyone can explain to me for future reference that would be good. I just need to add a check in the vbs file that determines whether it is a laptop or not. If System=Laptop then continue else end script. I will repost when I have worked this out. Change attachment to .vbs DellBattery.txt
  18. The problem we have got is that there are over 5000 users and we don't know exactly who has and where th laptops are located. I know you can't get the battery serial number through WMI, but you can gather information that will allow you to cut down the amount of machines that may need replacement. Thats the idea of this script. I would much rather go round 200 users to see if they need a replacement, rather than 5000+. It should save a lot of time running this script, I really just want to know, why I have to run it twice to get the text file to populate.
  19. @MRitter Mark, I mean all the variables that WPI can determine, such as %WPIPATH% %SYSTEMDRIVE% %WINDIR% %CDROM% or %CDDRIVE% %SYSTEMROOT% %TEMP% Can these be entered in the log file as: Variables detected by WPI as: %WPIPATH% = D:\$OEM$\WPI %SYSTEMDRIVE% = C: %WINDIR% = C:\Windows %CDROM% or %CDDRIVE% = D: %SYSTEMROOT% = C:\Windows %TEMP% = C:\Documents and settings\Kevin\Local settings\Temp Does anyone think this would be useful? I just think it will assist with the configuration of the cmd parameters within WPI
  20. Can WPI 5.4 output all the available variables to the WPI Log file and what they are returned as. This would be useful for command line syntax.
  21. You are 100% correct and I apologise for not saying this at the start. How do I do this guys? I wasn't critising WPI at all, I think it is a great project and really usefull. To be honest I thought it was something I was doing wrong and now WPI's fault at all. I will try and be more constructive in future though, thanks for the kick up the backside. If you could post me your compiled autoIT script that would be really useful.
  22. I don't know if you have seen the news today about Dell recalling millions of laptop batteries. Article can be found here: http://news.bbc.co.uk/1/hi/business/4793143.stm I have been tasked with writing a script that will determine if the PC/Laptop is Windows XP as I think WMI is only installed on WinXP and above, (might be wrong) If it is WinXP, it will then launch a vbs script that will collect information such as: I need to put a check for checking if machine is a laptop or desktop, if laptop continue running script, if desktop quit. (any assistance with this appreciated) Computername Username OS Caption OS Version Laptop Manufacturer Laptop Model Battery Manufacturer Battery Name Battery Device ID All of this information is outputted to a file called %computername%.txt and thn a copy of this file is made to %Temp% I am having a problem where if the vbscript is run once and the %computername%.txt file doesn't already exisit, I get a permission denied error. (It creates the .txt file, but doesn't enter any information). However if I then run the vbscript again with the .txt file already created, it works fine. Can someone tll me what I am doing wrong cos it is really bugging me. It hasn't been decided how this script is going to b launched yet, but I am 99% certain it will be kicked off by Kix login scripts. Is there a way for th batch file that Kix launches to determine whether or not machine is laptop or desktop? I think there is a WMI command line engine, but can't remember exactly. Once we have collected all these %computername%.txt files accross the council, we then would like to import all of these files into 1 csv file. From this file we will then try and determine exactly what customrs need to be contacted to arrange replacement battries. I can't beleive there isn't a solution for this from Dell. I know they have a webpage, but that relies on the person having access to the internet. I was hoping that a WMI script could find out the serial number of the battery, but it appears not to drill down that far. DellReplacement.zip
  23. GSH, can you tell me how you complied the script as an executable. I think I might change the hta's I am using in an automated build .exe for security.

  • Create New...