p4ntb0y

I have a NAS 1200s Fitted with 4x 250GB IDE Drives. I would like to have the following config.... all disks to be dynamic. a mirrored partition of 20GB on the first two disks. then disk 2,3 and the rest of the space on disk 1 and 0 to become one volume. I am really getting a bit pee'd with this, does anyone have this similar setup? Its easy to do in comp disk manager, I just can replicate it within the diskpart cmd line.

well if you had HP kit you could use biosconfig.exe. This will switch your boot order.

yep I am going to do it by a script.

I could but.... I noticed the other day when i booted a a laptop with winpe 2005 and I tried winpe 2 that the disk 0 was my external drive and not the master drive in the laptop so thi worries me cause knowing the biffs that work here they just run the batch file can not check

Hi, Does any know of a Diskpart gui for windows 2005? I know that diskpartitoner is out there but this does not work on my windows 2003 sp1 version of diskpart so i went down a version and now at least it can see the disk's But when I click on some of the actions it just seems to hang. So is there a gui around that some one has that will work with the 2003 version of diskpart? The reason you ask well our engineers cough "desktop placer's" think its to to difficult to use the cmd line.

Just to confirm that I have used the Broadcom RIS driver and this works on a DL380 G5 Windows 2008 is just down the road so more support will be out soon been to my MS Partners windows 2008 comf I spoke to the MVP there and he reckons that you be able to create your own winpe boot wim and there be more support nearer Nov time when it Windows 2008 ships... So hopefully HP will jump on the wagon and sort the smart start scripting toolkit for winpe 2.0 which I reckon will actually work! depending on the not so good hp CHM'S/DOCS Windows 2008 Core is so looking good but thats another topic.

Yep diskpart> sel disk 0 create part pri active assign letter=c then format then apply image

you could use a script to join it to the domain depending on how your domain OU's are set up for instance based on the computer name "trigram" FINPC1000" this will join my pc to the "fin" OU. My you could go further and use the bdd and join the machine to the domain based on Mac address name, model or serial number etc. however there is more setup required for this. We have SMS 2003 OSD FP for our replace "OS" RIS/WDS For "F12" pxe boot winpe 2> base image on the machine this then runs a SQL script to get wsname.exe from the bdd database (using sql 2005 but you can use msde) this then fills in the name and drivers for that model and mac address, I also dump al the info from the machine, drivers, serial number, hal, asset, firmware versions etc back to the bdd database so I have all the asset details to make me ITIL compliant. I can then update SMS so that my base machine gets its LOB Apps (Line of Bussiness Applications) based on the information held in the bdd database. Its a very good tool i recommend it to any enterprise admin My base wim image is 400MB without the i386 I distro this out to my sites using SMS and DFS Shares. It does take abit to set set up but all the job aids and doc's are in the install as well as all the sql queries.

@dkreifus yes we can do lite touch ms speak. How are you deploying your image. is it wim based (file based) or ghost (sector based) we could boot winpe 2 and using the startnet.cmd add the cmd to cut your disk how you want it and then apply the image and then run ztihaldect.vbs. your journey must near its end? Not sure but you can sysprep a box three times good practice would be to capture the master first then do a sysprep.

ok say you have a machine that is....ACPI Uniprocessor PC", ACPI APIC UP HAL (Halaacpi.dll) or...ACPI Multiprocessor PC", ACPI APIC MP HAL (Halmacpi.dll) go into device manager and click on my computer and change the hal type to... "Advanced Configuration and Power Interface (ACPI) PC", ACPI PIC HAL (Halacpi.dll) this will not ask for any additional files. Sysprep your machine and then deploy to an.. "Advanced Configuration and Power Interface (ACPI) PC", ACPI PIC HAL (Halacpi.dll) run either script from johan or trtkron within winpe. there is no reason why this would not boot on a "Advanced Configuration and Power Interface (ACPI) PC" The script would not make any changes to the sysprep.inf file as no change of hal is required. Now try the same image onto a "ACPI Uniprocessor PC" and run the script this will update the unattend section of your sysprep and add the following "UpdateUPHAL = "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" now I know your wondering %windir%\inf does not contain my files well the files are taken from the dllcache folder. Please put my mind at rest and try this lol sorry If I come across a bit harsh I only mean to help :-)

oh my god! this is madness! like trtkron said.... just change the hal and run the script think about it when you change your apic_up or apic_mp hal to apic does it ask for installation files or does it do it automactically? So where do you think these files come from? This has never failed for me and I got 10 different laptops and 20+ Desktops. Again I have never renamed any files nor copied them from CD or have an i386 anywhere near my images. unless Johan Arwidmark MVP is wrong? maybe he is? all I know is he help me alot and his script and comments helped me consolidate all my images into one using ghost or wims. @DKREIFUS Please can you do a devcon on all your machines you want as one image. Then run Device hwids and I will knock up the script you need and the sysprep entries you need also for mass storage devices. if you like?

Multicasting winpe 2 now thats a great idea!

sorry for the late reply.. I have only got the mount thing working when the waik is installed on your machine. I will be releaseing a new version which is just about finished. the finished version and open source will be avaiable later this week. As before this does not use any API Calls, however I am trying to learn a c++ so that I can use API's from the wimgapi.dll but like like everything trying to learn a new langauge, and exams to study for it may be some time. But the new version looks plain but works for my Engineers and me.

Oh dear you dont have to rename files etc. Seal your image as "Advanced Configuration and Power Interface (ACPI) PC" run your script. no need to get files from the cd etc its in the dllcache folder. works fine for me. May I suggest your problem lies eleswhere? if you seal your machine as ACPI then you have the correct HAL allready and that it should boot ok even if it was not the right hal your get a stop error or loop. If you get a 7B Stop error then this will be a mass storage related driver issue. I ran a test as follows... Built a Ref machine DC5700 and a D500 both HP. one use's the ACPI Multiprocessor PC - ACPIAPIC_MP and the other use's ACPI Uniprocessor PC - ACPIAPIC_UP. I changed the HAL on both computers to be "Advanced Configuration and Power Interface (ACPI) PC" (So all my hal.dll files are in the dllcache) I did this by going to Device manager then expanded "computer" update driver, and manually select "Advanced Configuration and Power Interface (ACPI) PC". Syspreped my machine and captured with imagex. booted my NC6000 UP with winpe 2 (With wmi and scripting support) ran the ztihaldetect.vbs and echo'ed out the key it reads in my case for the NC6000 it was "acpipcic" so the script does nothing to sysprep. nc6000 booted up fine. Tried a DC7600 and a NC6400 and a D500. The NC6400 reported back as "ACPIAPIC" the script then updated the sysprep in the unattend section. I did not add or rename any files I don't even have an i386 on my image. And it booted fine well I actually forgot about the storage drivers on the first test (7B Stop error) But the second test was fine. DC7600 did the same booted fine, checked the HAL on start up and it was "ACPIAPIC_MP" Which is correct. D500 did the same booted fine, checked the HAL on start up and it was "ACPIAPIC_UP" Which is correct. So everything worked fine. Add this to the script wscript.echo sHalType(0) between If sHalType(0) = "acpiapic" Then sHalType = oWshShell.RegRead("HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL000\HardwareID") Oh yeah where credit is due Johan Arwidmark..... A geeks guide to Windows XP HAL Replacement I beleive your having troble with the IBM T42 I am not sure what typ of HAL that model has? Again if you have problems your welcome to PM me and I will be all to happy to help this is easy, supporting all the HAL Types now that is a nigtmare! This works fine but is not supported by Microsoft. on a side note did you solve your problem with the sata native mode? for the 945 chipset namly the ICH7M/ICH8M? f you add the following to your sysprep... [SysprepMassStorage] ; ; Added for NForce4 ATA support ; PCI\VEN_10DE&DEV_0055&CC_0101=C:\Drivers\NVATA\nvata.inf PCI\VEN_10DE&DEV_0054&CC_0101=C:\Drivers\NVATA\nvata.inf PCI\VEN_10DE&DEV_0267&CC_0101=C:\Drivers\NVATA\nvata.inf PCI\VEN_10DE&DEV_0266&CC_0101=C:\Drivers\NVATA\nvata.inf PCI\VEN_10DE&DEV_037F&CC_0101=C:\Drivers\NVATA\nvata.inf ; ; Added for NForce4 RAID support ; PCI\VEN_10DE&DEV_0055&CC_0104=C:\Drivers\NVRAID\nvraid.inf PCI\VEN_10DE&DEV_0054&CC_0104=C:\Drivers\NVRAID\nvraid.inf PCI\VEN_10DE&DEV_0267&CC_0104=C:\Drivers\NVRAID\nvraid.inf PCI\VEN_10DE&DEV_0266&CC_0104=C:\Drivers\NVRAID\nvraid.inf PCI\VEN_10DE&DEV_037F&CC_0104=C:\Drivers\NVRAID\nvraid.inf ; ; Added for NForce4 SMBus support ; PCI\VEN_10DE&DEV_005E=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_00A4=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_00D3=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02F0=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02FE=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02F8=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02F9=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_027E=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_027F=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02FF=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_0270=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_0272=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10DE&DEV_02FA=C:\Drivers\NVSMBus\nf4sys.inf PCI\VEN_10de&DEV_01b4=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_0064=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_00D4=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_0084=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_00E4=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_0052=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_0034=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10de&DEV_0264=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10DE&DEV_0368=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10DE&DEV_03EB=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10DE&DEV_03F4=C:\Drivers\NVSMBus\nvsmbus.inf PCI\VEN_10DE&DEV_8352=C:\Drivers\NVSMBus\nvsmbus.inf ; ; Added for Intel SATA Controller Support ; PCI\VEN_8086&DEV_2652&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2653&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_27C1&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_27C5&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2681&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2821&CC_0106=C:\Drivers\IntelSATA\iaahci.inf PCI\VEN_8086&DEV_2652&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_27C3&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_2682&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_27C6&CC_0104=C:\Drivers\IntelSATA\iastor.inf PCI\VEN_8086&DEV_2822&CC_0104=C:\Drivers\IntelSATA\iastor.inf ; ; Added for ich5ide Controller Support ; PCI\VEN_8086&DEV_24D1 = C:\Drivers\IntelInf\ich5ide.inf PCI\VEN_8086&DEV_24DB = C:\Drivers\IntelInf\ich5ide.inf PCI\VEN_8086&DEV_25A2 = C:\Drivers\IntelInf\ich5ide.inf PCI\VEN_8086&DEV_25A3 = C:\Drivers\IntelInf\ich5ide.inf ; ; Added for ich6core Controller Support ; PCI\VEN_8086&DEV_2640 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2641 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2642 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_266A = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2660 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2662 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2664 = C:\Drivers\IntelInf\ich6core.inf PCI\VEN_8086&DEV_2666 = C:\Drivers\IntelInf\ich6core.inf ; ; Added for ich6usb Controller Support ; PCI\VEN_8086&DEV_2658 = C:\Drivers\IntelInf\ich6usb.inf PCI\VEN_8086&DEV_2659 = C:\Drivers\IntelInf\ich6usb.inf PCI\VEN_8086&DEV_265A = C:\Drivers\IntelInf\ich6usb.inf PCI\VEN_8086&DEV_265B = C:\Drivers\IntelInf\ich6usb.inf PCI\VEN_8086&DEV_265C = C:\Drivers\IntelInf\ich6usb.inf ; ; Added for ich7ide Controller Support ; PCI\VEN_8086&DEV_27C0 = C:\Drivers\IntelInf\ich7ide.inf PCI\VEN_8086&DEV_27C4 = C:\Drivers\IntelInf\ich7ide.inf PCI\VEN_8086&DEV_27DF = C:\Drivers\IntelInf\ich7ide.inf ; ; Added for ich8core Controller Support ; PCI\VEN_8086&DEV_2810 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2811 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2812 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2814 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2815 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_283F = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2841 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2843 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2845 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2847 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_2849 = C:\Drivers\IntelInf\ich8core.inf PCI\VEN_8086&DEV_284F = C:\Drivers\IntelInf\ich8core.inf ; ; Added for ich8smb Controller Support ; PCI\VEN_8086&DEV_283E = C:\Drivers\IntelInf\ich8smb.inf ; ; Added for ichXdev Controller Support ; PCI\VEN_8086&DEV_537C = C:\Drivers\IntelInf\ichXdev.inf ; ; Added for ich5usb Controller Support ; PCI\VEN_8086&DEV_24D2 = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_24D4 = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_24D7 = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_24DE = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_24DD = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_25A9 = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_25AA = C:\Drivers\IntelInf\ich5usb.inf PCI\VEN_8086&DEV_25AD = C:\Drivers\IntelInf\ich5usb.inf ; ; Added for ich6ide Controller Support ; PCI\VEN_8086&DEV_2651 = C:\Drivers\IntelInf\ich6ide.inf PCI\VEN_8086&DEV_2652 = C:\Drivers\IntelInf\ich6ide.inf PCI\VEN_8086&DEV_2653 = C:\Drivers\IntelInf\ich6ide.inf PCI\VEN_8086&DEV_266F = C:\Drivers\IntelInf\ich6ide.inf ; ; Added for ich7core Controller Support ; PCI\VEN_8086&DEV_27B0 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27B8 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27B9 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27BD = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27DA = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27D0 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27D2 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27D4 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27D6 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27E0 = C:\Drivers\IntelInf\ich7core.inf PCI\VEN_8086&DEV_27E2 = C:\Drivers\IntelInf\ich7core.inf ; ; Added for ich7usb Controller Support ; PCI\VEN_8086&DEV_27C8 = C:\Drivers\IntelInf\ich7usb.inf PCI\VEN_8086&DEV_27C9 = C:\Drivers\IntelInf\ich7usb.inf PCI\VEN_8086&DEV_27CA = C:\Drivers\IntelInf\ich7usb.inf PCI\VEN_8086&DEV_27CB = C:\Drivers\IntelInf\ich7usb.inf PCI\VEN_8086&DEV_27CC = C:\Drivers\IntelInf\ich7usb.inf ; ; Added for ich8ide Controller Support ; PCI\VEN_8086&DEV_2820 = C:\Drivers\IntelInf\ich8ide.inf PCI\VEN_8086&DEV_2825 = C:\Drivers\IntelInf\ich8ide.inf PCI\VEN_8086&DEV_2828 = C:\Drivers\IntelInf\ich8ide.inf PCI\VEN_8086&DEV_2850 = C:\Drivers\IntelInf\ich8ide.inf ; ; Added for ich8usb Controller Support ; PCI\VEN_8086&DEV_2830 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_2831 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_2832 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_2834 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_2835 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_2836 = C:\Drivers\IntelInf\ich8usb.inf PCI\VEN_8086&DEV_283A = C:\Drivers\IntelInf\ich8usb.inf And then download the "Intel® Matrix Storage Manager" package from the intel site follow the instructions to extract the files. Then you will not have to turn off SATA native support in the bios. again thanks to Johan Arwidmark

I beleive that M$ Copy each wim to a temp drive on the target machine. The trick here is to find out how to get the spilt wim info to find out the amount of cds required.

Jazkal, Is a man that thinks outside the box :-)

just a litle update on what the gui looks like at the moment. screenshots.... I am going to add the option for the different compressions I think. The WimInfo button gives you all the info about WIMS in a nice laid out window from the xml output this includes total sizes so I may use this option for the split wims accross CD's /DVD's The check wim on capture option is the the checkdisk option I really want to be able to convert the c++ header file for the wimgapi.dll api's to vb6 any takers on this? what other options would be needed? diskpart GUI to go along side this? map network share? inject drivers option? change hal option?

I have to do a test this week as I have new drivers based on 2008 so need to add these to my winpe 2 image then try the ssstk. I keep you posted.

Nearly done a new version of this GUI. I have binned the transparent window. Added an option for Checkdisk. And as soon as I have worked out the split wims that will be an option as well. Was thinking of adding support to intergrate drivers and change HAL type. any other options reguired? Once finsihed I will post it.

wow! you guys are making good progress sorry for my late delay! Anyhows I am at the state now of adding split wim support in my VB Imagex GUI and reading some of the posts it should be a bit easier to implement. As M$ can do it I am sure we should be able to do it. I will post the code here as soon as I have a solution as long as you like vb6 :-)

Well you need to tell us what version of PE your using? Also how big is your PE at the moment?

Hi guys I have a Imagex gui here which I hope you will like. The whole thing has been re-done all the code has been done in VB6. This has been tested in vista pe and winpe 2005. here are a couple of screenshots... Added different compression types. As you can see you can Mount Images, extract well do everything that the cmd line imagex can do, as all that the code does is call imagex behind the GUI, The cmd for imagex will be displayed at the botton of the gui for debug. Anyone that would like to have the source files are welcome please PM me and I will mail you untill I can host them somewhere. The current size is 1.5mb I have added a place on the front of the gui so that you can place a OEMLOGO.JPG for your company or yourself (I made a mistake and left it at jpg instead of bmp trtkrom was kind enougth to post the VB6 api calls, I am way out of my depth here with the coding :-( You do need the following files within the same location.. imagex.exe intclg.exe winfltr.ini winfltr.sys wimgapi.dll COMDLG32.OCX MSCOMCTL.OCX MSVBVM60.DLL tabctl32.ocx and if you want to add your own exclude list... include a custom Wimscript.ini file If you would like the Source files then Please PM me and I will send it out. The above ocx and dll files apart from wimgapi are included. This is all I have at the moment which is a a bit lame as I need to learn a hell of a lot more vb and c++ I would be willing to fund a project if someone can code a proper gui with api calls and a progress bar! I have included a new attachment but it does not have the MSCOMCTL.OCX or MSVBVM60.DLL due to the size OnDansWIM.rar

We have just recently installed a SAN Solution over two sites with Cluster servers for failover and ESX to run some Virtuals I believe that the cost was under 30K not including software. Odviously it will depend on what size disks your require and the connection between your site. I am in the UK if you want to PM me I will see If I can dig out the quotes and docs for it. We used HP MSA 1000 one at each site. with 2x DL380 G5's at each site these run very fast I am very impressed with them so far. It sounds to me you need a entry to mid-range solution I think 40K is well in your sights. PS Dont forget to budget in your backup solution mayeb a LTO3 Autoloader depending on the amount of space you need. What excalty are you doing anyways? as there is more than one way to do things.

Well I have used it to backup my laptop running vista and my desktop I even use it for Server Backup snapshots had no problems yet.

recently I wanted to assign a letter to a USB drive which that device would allways get, just like the x: for the ram drive. while on google,I found a great little proggie called USBDLM V3.4.2 link Here its very simple to do and works in Winpe 2005 and Winpe 2.0 all you have to do is call _install.cmd this runs usbdlm.exe and installs it as a service. Now locate you USB drive and then open up the sample USBDLM_sample.ini file and adjust the settings how you want them IE:- Allways assign U: to USB Drives rename this file to _USBDLM.ini and place it on the root of your USB drive. Once your in winpe 2.0 plug your drive in and it will allways use the letter you have assigned :-) Very useful if you have big images or no dvd rom. You will have to check the Lincencing to see if you can use it in your enviroment.