Purpose of Integrating eCATT and QTP?

Hi Gurus,
I would like to know what is the purpose of integrating QTP and ecatt (OR) when do we go for integration of QTP and eCATT?
Please help me on this?
Regards,
GS...

>
Get Started wrote:
> Hi Gurus,
>
> I would like to know what is the purpose of integrating QTP and ecatt (OR) when do we go for integration of QTP and eCATT?
>
> Please help me on this?
>
> Regards,
> GS...
Hi GS,
1)There are cases where eCATT will support certain applications like web-based application and hence we use QTP which support this application.
To put it short,eCATT works excellent with SAP application and if you need to interface applications outside SAP,you can use QTP.
2)You have to enable setting for the third-party tool.Reach out to your basis team member.
   Once setting is made,you should be able to see the QTP tool and you can use the same for recording.
For more information,please refer SAP portal.
Regards,
SSN.

Similar Messages

  • ECATT and QTP integration isuue

    Hi,
    I am trying to execute QTP Scripts through eCATT. In this regard i have done the following settings
    Check whether or not you have the roles - SAP_ECAT, SAP_ECET and SAP_ECST in your login id.
    Check the patch levels, support packages of the system
    Check the external tool parameters in the ECCUST_ET table
    Note : The mode of execution for external tool should be 'A' - With surface of external tool in the start options "
    when i tried to eaxeute from eCatt i got the error called "Failure Starting Quick test professional"
    Please any one help me on this............
    Thanks and Regards
    Dileep

    Hi Dileep,
    Kindly go through this article /people/community.user/blog/2007/01/15/integrating-ecatt-mercury-qtp-part-2 , you will be able to sovle few of your issues .
    As i have done project on QTP/eCATT intergration mode .
    The major issues will be .
    1) Performance wise it will be slow , as you will be invoking QTP script from eCATT.
    2) You will face problem with format compatibility .
    I hope , the information solves some of your problem.
    regards
    Harsha

  • Ecatt and QtP

    Dear all,
    I am trying to use Qtp and ecatt . I have made the required settings in Qtp and Ecatt.
    I am also able to record the script using Qtp and the script is getting created in sap system.
    I have also created the User Ecatt_et_usr still when i execute the script directly in ecatt i get the following error
    " Failure when starting quicktest professional".
    Can u please suggest me a way out.
    thanks and regards,
    Priya

    Check whether or not you have the roles - SAP_ECAT, SAP_ECET and SAP_ECST in your login id.
    Check the patch levels, support packages of the system
    Check the external tool parameters in the ECCUST_ET table
    Note : The mode of execution for external tool should be 'A' - With surface of external tool in the start options
    Have a look at this blog: /people/community.user/blog/2007/01/22/integrating-ecatt-mercury-qtp-part-3
    I followed the checklist religiously and things worked out fine for me this first attempt itself.
    This is a straight forward integration and should work without creating any hassles
    Good luck and hope I could be of some help

  • ECATT and QTP integration.

    Can any one tell me what is SAP BASIS 620 Support Package level requirement for eCATT & Mercury QTP integration.
    Currently we are running eCATT on R/3 4.7 with SAP BASIS Support Package SAPKB62003.
    But when we are trying to integrate QTP 6.5 with eCATT it gives following error
    (we have done all the required configurations) :
    From QTP to eCATT :
         "The eCATT server you specified does not have the required support. Select another eCATT server or install a later version of eCATT on your server."
    From eCATT to QTP :
         "Error During Method Call in OLE API."
    Also suggest if we are making some other mistake.
    Thanks in advance.
    Regards
    Naivedya

    Hi Naivedya,
    The following are the minimum requirement with package leves.
    Release 6.20  Support Package SAPKB62003
    Release 6.10  Support Package SAPKB61017
    Release 4.6D  Support Package SAPKB46D21
    Release 4.6C  Support Package SAPKB46C32
    I am also getting the same error, even i have latest version.
    Thanks,
    Mahantesh

  • Integration of eCATT and QTP

    Hello ,
    Can anyone kindly let me know as to how to call QTP scripts from eCATT ?.
    i searched on the net but i did not got an simple material .
    Regards
    harsha

    Hello,
    Please start the transaction SECATT in the system and then enter the test script name you want to create along with the right version and there is option to select External tool in the SECATT screen , select the QUICK TEST PROFESSIONAL tool, before this make sure that the QTP tool is installed in your system.
    Once all the data is mentioned click on the create button and then specify the mandatory parameters and then click on the script button in the tool bar , this takes you to the QTP tool where you can perfrom the required recording and then transfer the data to eCATT , once the recording is complete the QTP command appears in the script and then you can save the script and then execute the eCATT script as usual.
    Thanks & Best regards,
    Ajay

  • ECATT and Transaction WAK1

    Hey all,
    I'm attempting to use eCATT to create promotions via transaction WAK1 and have run into a problem that I need help with.  During the recording, I need to make changes to the long text field in the header details.  To do this properly (and to get the fields to appear in the BDC) I need to click the SAP Script button which will take me into the older style editor.  This brings back the text I typed in the editor in the BDC so that I can edit it for the next promotion I create.  The problem is that it always overwrites what I put in the BDC with what was recorded initially.  I have even gone through the upload in the foreground and I can see that my entries from the BDC are entered into the transaction, but when I go back in again the text has reverted to the text from the original recording. 
    Is this something to do with the other data that eCATT stores for it's recordings?  Is there any way to modify or delete this so that I can provide different text for the promotion?
    Crossing fingers for a positive response.
    Thanks,
    Tim

    Hi
    check these link,
    eCATT- An Introduction
    /people/sumeet.kaul/blog/2005/07/26/ecatt-an-introduction
    Creating Test Scripts
    /people/sumeet.kaul/blog/2005/08/10/ecatt-creating-test-scripts
    eCATT Logs
    /people/sapna.modi/blog/2006/04/18/ecatt-logs-part-vi
    eCATT Scripts Creation – TCD Mode
    /people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation-150-tcd-mode-part-ii
    Creation of Test Data Container
    /people/sumeet.kaul/blog/2005/08/24/ecatt-creation-of-test-data-container
    eCATT Scripts Creation - SAPGUI Mode
    /people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii
    Integrating ECATT & MERCURY QTP Part -1
    /people/community.user/blog/2007/01/02/integrating-ecatt-mercury-qtp-part-1
    Using eCatt to Test Web Dynpro ABAP
    /people/thomas.jung/blog/2006/03/21/using-ecatt-to-test-web-dynpro-abap
    and
    -command reference
    http://help.sap.com/saphelp_nw04/helpdata/en/c6/3c333b40389c46e10000000a114084/content.htm
    /people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i
    http://prasadbabu.blogspot.com
    https://www.sdn.sap.com/sdn/developerareas/was.sdn?page=test_tool_integration_for_sap_e-catt.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm
    http://www.erpgenie.com/ecatt/index.htm
    hope this helps.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • ECATT  versus  QTP

    eCATT and QTP are both automated testing tools.
    eCATT can be used only to test SAP GUI, where as with QTP we can test other appplications also.
    My question is when do we go for eCATT and when do we go for QTP?
    And what is the reason for integrating eCATT with QTP?
    And when we opt for QTP for testing SAP, what is the advantage over eCATT?
    Thanks in advance
    anyone please answer my question
    Message was edited by:
            kumar kumar

    Hi,
    1.eCATT is used to test the SAPGUI based transactions.
    2.If web based transactions such as CRM ISA, SRM EBP applications are involved, then QTP has to be used.
    3. In scenarios where the End to End testing has to be performed using automation starting with Web Frontend to middleware interfaces and backend SAP Transactions such as delivery/shipping, we need to integrate QTP with eCATT.
    Please take a look at this nice blog about QTP->eCATT integration.
    /people/community.user/blog/2007/01/02/integrating-ecatt-mercury-qtp-part-1
    Thanks
    Sudhan Shan

  • ECATT and Mercury QTP integration.

    Hi All,
    We are evaluating the SAP eCATT and Mercury integration part for one of our project. So we have downloaded the following:
    1. Mercury QTP version 9.1 (14 day trial version)
    2. Mercury SAP Addin.
    The SAP status is as follows:
    1. SAP 4.7 Versions.
    (a)SAP BASIS at patch level 48
    (a)SAP ABAP at patch level 45
    (a)SAP APPL at patch level 20
    2. SAP Logon For Windows ( 640 Final Release ) ,Patch level - 23.
    We have done the entire configuration at the SAP level like
    1. Making "sapgui/user_scripting" value TRUE.
    2. Creation of entry in ECCUST_ET table.
    3. Also created the user ECATT_ET_USR with the necessary Roles.
    After doing all this, when the ECATT is created with the "External Tool" option as "Mercury Quicktest Professional" it gives an error that
    "Quicktest Professional is Not installed or Does not have license"
    Please let us know whether we are missing any component which needs to be installed or if any other config is missing.
    Regards,
    Rupesh.

    Hi Kalyan,
    SAP eCATT is a automation tool meant for functional testing in SAP. It comes with WAS. Latest version is WAS 6.40. It is made in ABAP.
    QTP is Mercury's tool, which is a third party tool for automation testing. The language used here is VB Script.
    Both the tools are good. But the only drawback with eCATT as of now is that it can execute web based SAP transactions except web dynpro. So if the testing of SRM, CRM etc is involved, one is forced to use QTP.
    QTP takes the wrapping of eCATT and executes in SAP.
    If only SAPGUI based transactions are involved in testing than eCATT is the best tool to be used. And if web based transactions are also involved, forced to go for QTP.
    Hope this clears your query.
    PS If the answer solves your query, plz close the thread by rewarding each reply.
    Regards
    Sapna Modi

  • QTP Integration - eCATT FUNction call

    Hello folks,
    I am pretty fit in eCATT, but I am fairly new to QTP. I setup an integration in a demo environment and QTP only let's me "open" eCATT Scripts that were recorded with QTP. If I am recording eCATT with QTP i am limited to UI Recording via SAPGui Scripting.
    Is there a way to call other eCATT's from QTP, to use more powerful eCATT options, like BAPI & FUNction calls? Or to directly call BAPIs / Function modules from within QTP?
    Thanks!

    hi,
    "QTP only let's me "open" eCATT Scripts that were recorded with QTP"
    QTP will open only those scripts which it has created.
    it will not open an ecatt script which ecatt has created.
    also we generally use qtp scripts to record and automate and then call the qtp scripts in ecatt.this way helps us use the features of both qtp and ecatt.
    please revert back for any clarifications.
    regards,
    Rakesh..

  • ECATT and Quick Test Pro Compatibility

    Hi All,
       From which version of QTP is the integration to eCATT feature available. Are all versions of QTP compatible with eCATT and all QTP scripts can be called within eCATT?
    Regards,
    Justin

    Hi Justin,
    I think from QTP 8.0 all versions of QTP supports eCATT.
    Not all scripts can be used in eCATT.
    Hope it helps.
    Regards,
    Venky

  • Difference between Integration Process and Monitoring Process

    Hi Experts,
    What is the difference between Integration Process and Monitoring Process available in PI7.1?
    SAP says that Monitoring process is a special kind of integration process that receives the event messages.
    My doubt is even integration process can receive the event messages.
    Why these two different type of entities are created for the same purpose?
    And what is the technical difference between the two in terms of PI perspective?
    Regards,
    Sami.

    My question is now answered.
    [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70a25d3a-e4fa-2a10-43b5-b4169ba3eb17]
    On page 17 of this pdf following sentence is mentioned :-
    From technical perspective, there is no difference between monitoring process and integration process.
    Though logically those are two deifferent things.
    Monitoring porcesses are used to receive only event messages that is comprises of event data only.
    Like Purchase order creation is a event and its event message will have the event data like Order Id, Created on, Created by, Quantity etc., instead of whole purchase order.
    Where as Integration Process is a way to provide solution in some specific circummtances like where we have to automate our process or where we need something in between for the course of communication.
    Guys thanks for your precious time.
    Regards,
    Sami.

  • ECATT Vs QTP

    Hi all,
    Can someone list the differenece of this tools and suggest which tool is best suited for a SAP World.
    I knew eCATT is good at SAP Transactions and it cant test web applications and QTP is good at both.
    I'm looking something more points then that...
    Regards,
    Venky

    Hi,
    ECATT is a automation tool meant for functional testing in SAP. It comes with WAS.
    QTP tool which is a third party tool for automation testing. The language used here is VB Script.
    The only drawback with ECATT as of now is that it can execute web based SAP transactions except WebDynpro.
    If the testing of SRM, CRM etc is involved, one is forced to use QTP.
    QTP takes the wrapping of ECATT and executes in SAP.
    SAPGUI based transactions are involved in testing than ECATT is the best tool to be used.
    And if web based transactions are also involved, forced to go for QTP.
    I think it would help you to some extent
    Edited by: Vagdevi on May 18, 2009 5:48 PM
    Regards
    R
    Edited by: Vagdevi on May 18, 2009 5:48 PM

  • Integrated ECATT-

    Dear Experts,
                        I have created ECATT for Sale order and Delivery ( Integrated ECATT) . Sale Order creating is going Thro. But I have faced some problem when the Delivery Script Is calling. My Posting Date and Picking Qty are not passed to that Particular Screen .
                        Is anbody faced the Same Problem, Let me know the Solution.
    With Regards,
    Selvan.S

    Hi selvan,
    I assume you have sales order and delivery recorded in TCD or SAPGUI in separate scripts.
    If so please continue with my comments..
    1.Please try executing delivery separtely by passing valid values,
    in case if parametes are not passed in screen.
    then this is a problem in your recording,please record it again or debug.
    2.Incase delivery script is working fine, please refresh once interface in integrated script and try passing values again.
    In case this does not help,please write little more in detail about your problem
    best regards
    vinay

  • Diff bet eCATT and LSMW

    Hello Guru's,
    Will anyone clarify me the diff between eCATT and LSMW ?.  shall we have eCATT for uploading Legacy data to R/3?.
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:08 PM

    eCATT is an SAP Testing Tool used to automate & test business scenarios in R/3. Each test generates a detailed log that documents the test process and results. If the testing is smooth without any errors, this means that the business scenarios mapped in R/3 are correct. If the test results in error then the problem can be analyzed using the error log that is generated.
    eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java.
    Features of eCATT:
    Following functions can be performed using eCATT:
    Test transactions, reports and scenarios.
    Call BAPIs and function modules.
    Test remote systems.
    Check authorizations (user profiles).
    Test updates (database, applications, GUI).
    Set up customizing tables.
    Test the effect of changes to customizing settings.
    Perform load testing.
    Check system messages.
    Integrated with Test Workbench, so allows proper management of scripts using SCAT transaction.
    Supports CATT migration to eCATT.
    All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
    eCATT Objects can easily download & upload in XML with XSD format.
    There can be several versions of Test Scripts, which allows different implementations with different releases.
    The separation of Test Scripts, Test Data & System Data allows for a considerable degree of reuse.
    All eCATT Objects are Repository Objects. Therefore one can take advantage of Standard SAP Transport Tools.
    eCATT Objects can easily download & upload in XML with XSD format.
    eCATT- An Introduction
    /people/sumeet.kaul/blog/2005/07/26/ecatt-an-introduction
    2) http://allaboutsap.blogspot.com/search/label/LSMW
    also u can findout many threads in the forum itself no need to wait for new posts(if u get, that also from forum itself)
    Thanks

  • HOWTO: Create a Boot Configuration That Has No Driver Signature Checks. Disable Driver Integrity Checks and Install a Custom Non-Signed Driver

    Hello,
    Recently, I had a task where I needed to install a custom non-signed driver onto my Windows 8 64-bit setup. As it is known, Windows has driver enforcement policies that, as a security measure, do not allow you to install non-signed drivers.
    I did not want to alter my current boot configuration so I decided to create a separate boot entry that would have driver signing policies disabled. For some reason I did not find any good source that would contain a step-by-step instruction on completing
    this task, so I decided that I'd better share my experience here.
    Lastly, there are multiple ways how you could turn off driver enforcement policies, but I find the way to do this via boot manager.
    Here's how you can do that.
    1. Press WindowsKey and type 'cmd' (without quotes) to find Command prompt, then click Command prompt icon. If you have User Account Control turned on, hold Ctrl+Shift keys pressed when clicking the icon.
    This will force Windows to ask you for elevation of command prompt. Elevation is necessary for editing Boot Configuration Database (BCD), the database used by Windows boot manager to store boot settings.
    2. In the User Account Control window click Yes to confirm elevation of command shell.
    3. At the command prompt type
    bcdedit
    to list your BCD entries.
    This will give you an output like:
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    The section that starts with Windows Boot Manager lists current settings for the boot menu. Here you find what boot entry is chosen by default, this is the one what you will boot into if you do not select any boot entry in the
    boot menu.
    The following record
    default {current}
    indicates that by default my Windows boots into configuration which I use at the moment (currently booted Windows configuration).
    To find out what exactly is current configuration, look into the list of boot entries, records that contain boot loader configuration and are titled as Windows Boot Loader in the bcdedit output.
    For example, the entry shown above is one of my boot configurations. This is one of the boot entries listed on the boot manager screen when I start my PC and it looks like:
    Windows Boot Loader
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8prowmc01.vhdx
    path \Windows\system32\winload.efi
    description Windows 8
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5d1-fb29-11e1-a74d-f2c962d62240}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8prowmc01.vhdx
    systemroot \Windows
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    This record has a unique GUID identifier that can be used to reference this boot entry, which is:
    identifier {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    If we look at the Windows Boot Manager settings, we'll see this entry is the first in order to be displayed in the boot menu on OS start (I marked the unique bits):
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    It references my VHD drive, a virtual hard drive where my Windwos 8 setup is residing:
    device vhd=[D:]\win8prowmc01.vhdx
    And it also specifies that the boot manager must use UEFI BIOS extension code to access my Windows boot partition:
    path \EFI\Microsoft\Boot\bootmgfw.efi
    3. Now locate the current boot entry.
    Current boot entry contains boot settings used to boot into Windows configuration to which you are currently booted. It is referenced in the list of boot entries as a Windows Boot Loader record that has the {current} keyword inside and may
    look like:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Because we are more than happy with current configuration and want to base our new boot configuration on these settings, we need to copy this boot entry ({current}) to a new boot entry.
    This is done by running the following command:
    C:\Windows\system32>bcdedit /copy {current} /d "No Driver Signature Check"
    Parameter /d here indicates that the following sequence of characters specifies the display name for the new boot entry that we are creating. The name inside the double quotes will be displayed in the boot menu when you boot your Windows.
    In other words, if you know restart your system, you'll see the new No Driver Signature Check in the boot menu.
    When copied, the entry is automatically given a new GUID identifier, so upon running the command above, you'll see the following line returned (you'll have an other GUID since these are unique identifiers):
    The entry was successfully copied to {a329b5d8-fb29-11e1-a74d-f2c962d62240}.
    4. Make sure the entry has been successfully created.
    Run the same bcdedit. (You may specify /enum or /v, or both /enum /v parameters at the prompt to get more detail about boot entries, but simple bcdedit is just enough to see the new entry):
    C:\Windows\system32>bcdedit
    Windows Boot Manager
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume2
    path \EFI\Microsoft\Boot\bootmgfw.efi
    description Windows Boot Manager
    locale en-US
    inherit {globalsettings}
    integrityservices Enable
    default {current}
    resumeobject {a329b5cf-fb29-11e1-a74d-f2c962d62240}
    displayorder {a329b5d0-fb29-11e1-a74d-f2c962d62240}
    {a329b5cc-fb29-11e1-a74d-f2c962d62240}
    {a329b5ca-fb29-11e1-a74d-f2c962d62240}
    {a329b5c2-fb29-11e1-a74d-f2c962d62240}
    {current}
    {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    toolsdisplayorder {memdiag}
    timeout 30
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    The entry has been created and given a unique a329b5d8-fb29-11e1-a74d-f2c962d62240 ID. It now has exactly same boot settings as the boot entry we used to boot into current configuration of Windows.
    5. Modify created  No Driver Signature Check entry and specify that Windows must have driver integrity checks disabled when booted using this boot entry.
    Any modifications to boot entries are made using /set parameter. To indicate that we modify a specific boot entry, we must specify the GUID for the No Driver Signature Check record, which is:
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    In other words, to edit (add or change) an option for the boot entry, we need to use the following command syntax:
    C:\Windows\system32>bcdedit /set GUID <boot_option> [<option_value>]
    First, we must specify that we don't want integrity checks be made. This is done by adding the loadoptions option and setting it to DISABLE_INTEGRITY_CHECKS value:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} loadopti
    ons DISABLE_INTEGRITY_CHECKS
    The operation completed successfully.
    6. Verify that load option has been added.
    Run the bcdedit command:
    Windows Boot Loader
    identifier {current}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description Windows 8 Enterprise RTM
    locale en-US
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    7. Add the option that turns on test signing mode and disables checks of driver signature.
    Adding the testsigning option and setting it to ON does the trick for us:
    C:\Windows\system32>bcdedit /set {a329b5d8-fb29-11e1-a74d-f2c962d62240} TESTSIGNING ON
    8. Now we have a boot entry that enables Windows not to do integrity checks and digital signature validation.
    We check it by running bcdedit:
    Windows Boot Loader
    identifier {a329b5d8-fb29-11e1-a74d-f2c962d62240}
    device vhd=[D:]\win8rtm.vhdx
    path \Windows\system32\winload.efi
    description No Driver Signature Check
    locale en-US
    loadoptions DISABLE_INTEGRITY_CHECKS
    inherit {bootloadersettings}
    recoverysequence {a329b5c3-fb29-11e1-a74d-f2c962d62240}
    integrityservices Enable
    recoveryenabled Yes
    testsigning Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice vhd=[D:]\win8rtm.vhdx
    systemroot \Windows
    resumeobject {a329b5c1-fb29-11e1-a74d-f2c962d62240}
    nx OptIn
    bootmenupolicy Standard
    hypervisorlaunchtype Auto
    9. Type 'exit' without quotes to exit from command prompt, and restart Windows.
    Upon booting you will be present with a new boot option to start Windows in configuration that allows you to install custom non-signed drivers.
    Hope this will help anybody to create their own custom boot configurations.
    Well this is the world we live in And these are the hands we're given...

    Hi,
    Thank you for sharing the solutions & experience here. It will be very beneficial for other community members who have similar questions. 
    Regards,
    Kelvin hsu
    TechNet Community Support

Maybe you are looking for