Configure Check-In disabled

hello everybody,
i'm configuring my CMS for a ISA project.
When i try to set check in part and press Configure Check-In button, the pop up appared but all field are disabled.
I cannot configure directory.
Where is the problem?
any suggestion?
thanks
Alex

assign nwdi administrators group to yourself

Similar Messages

AppContainers_test fails with error during pre-test configuration checks

Hello,
AppContainers_test fails with error during pre-test configuration checks:
"[FAIL] The machine is not properly configured for testing: the test directory "C:\Windows\SYSTEM32\" is not ACL'd to allow execute permission for "APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES"
But that kind of permission for APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES was allowed, also i tried to allow full access, but error was the same.
In the test WindowsFilteringPlatform_Tests, the same requirement "REQ - Wfp-based products must not block App Container apps operating within their declared network intentions by default" was checked successfully.
How can i pass successfully AppContainers_test?
I installed lastest versions of QFE and filters on my server, but it didn't help.

Hi M'Alerter,
I have the same issue, have you found a solution to your problem ?
Cheers,
Ghalem

Configuration Check Error in Managed System Configuration

Hi dear experts,
I come across a problem as the screenshot shows blew:
I check some relevant information, but no issues found:
1.
DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
saphostexec running (pid = 7094)
sapstartsrv running (pid = 7097)
10:46:34 24.06.2014 LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
saposcol running (pid = 7130)
DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
SAPSYSTEMNAME = SAP
SAPSYSTEM = 99
service/porttypes = SAPHostControl SAPOscol SAPCCMS
DIR_LIBRARY = /usr/sap/hostctrl/exe
DIR_EXECUTABLE = /usr/sap/hostctrl/exe
DIR_PROFILE = /usr/sap/hostctrl/exe
DIR_GLOBAL = /usr/sap/hostctrl/exe
DIR_INSTANCE = /usr/sap/hostctrl/exe
DIR_HOME = /usr/sap/hostctrl/work
service/admin_users = daaadm
service/logfile_000 = /tmp/s
service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
And the version of hostagent is up-to-date.
2.The URL
- http://<SMDhost>:1128/SAPOscol/?wsdl
- http://<SMDhost>:1128/SAPHostControl/?wsdl
can be accessed.
3.The step 3 in managed systems configuration is executed successfully.
4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
Now I have no idea how to proceed, please give me some advice, thank you in advance.
Best Regards,
Pany Pan

Hi Pany
Kindly check the below two sapnote
1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
Moreover , you need to check/verify/maintain the parameter in configtool
ThreadManager -> MaxThreadCount
Total number of Diagnostics Agents * 2 + 50
1250
ThreadManager -> InitialThreadCount
Total number of Diagnostics Agents * 1.5
900
ThreadManager -> MinThreadCount
Total number of Diagnostics Agents
600
ConnectionManipulator -> maxSoTimeOutConnections
Total number of Diagnostics Agents * 1.35
810
ConnectionManipulator -> MaxParallelUsers
Total number of Diagnostics Agents + 50
650
In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki
guide check the section Required Solution Manager Java Stack Settings (Scalability)
I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
minthreadcount , maxSoTimeOutConnections.
With Regards
Ashutosh Chaturvedi

Configuration check error: The SMD Agent is not able to connect the Satellite System (J2EE stack)

Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
Arindam

Hi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam

Managed System SLM~ABAP is not configured (Step 10: Configuration Check)

When I try to spend the last procedure "Configuration Check" (item 10 - Managed System Configuration) I get here is only an error message
The definition of Technical System 'SLM~JAVA' is not correct: 'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
Outside Discovery issue: refer to SAP Note 1611483
Managed systems setup | Managed System Definition Status (post setup) | SYSTEM =SLM~JAVA
What a way such settings: Managed systems setup | Managed System Definition Status?
I probably know only the tab SapSolution Manager: Configuration-> Managed system configuration-> Technical systems, but there make these settings is not possible.
How do I resolve this is "must have at least one Software Component Version"?
ps said note (1611483) has been done, but apparently no effect brought

Hi Michael,
Can you please check below :
Correct Software Component version is displayed in LMDB -> Host - > Tab Installed Software.
Managed System setup -> Assign Diagnostic agent -> Check SAP Host agents (to enusre agent is running)
You may restart both Diagnostic and Host agent and check again after few minutes if data is updated.
Additionally please check below SAP notes which might help resolve the issue :
1890035 - Error "Host 'hostname' must have at least one installed Technical system" during the step 'Check Prerequisites'
1799138 - Solution Manager configuration check returns "The definition of Technical System '{SID}~{STACK}' is not correct: '{SID}~{STACK}' : Operating System '{OSName}' of Host '{hostname}' must have at least one Software Component Version"
Hope this helps.
Thanks & Regards,
Nisha

No Function Identifier maintained. Configuration check not possible

Dear PM team,
While doing the Equipment installation with goods movement through IE4N, transaction code, system throwing following error messages.
1. No function identifier maintained. Configuration check not possible
2. Message for the configuration check.
Please guide me where i did the mistake? and suggest me how to correct this error message, without doing the changes in message controls.
thanks & regards
JK

JK,
My guess is that you are using Configuration Control.
If so, then have a look at these transactions:
PeteA

Diagnostic Dashboard: SOA-OIM Configuration Check

Hi All,
I recently installed OIM 11.1.1.3 After installation when I try to search approval task, I am getting the following error:
<Warning> <oracle.iam.consoles.faces.mvc.common> <BEA-000000> <oracle.iam.platform.canonic.base.NoteException: An error occurred while searching tasks from the SOA Server.>
When I ran the check from Diagnostic Dashboard, I got the following result:
Test Name SOA-OIM Configuration Check.
Description Checks whether the details provided for SOA-wiring are valid or not.
Result Failed
Details
Invalid SOA parameters found in the configuration file of Oracle Identity Manager.
The following parameters are empty:
     RMI URL
     SOAP URL
     Weblogic Username
     Weblogic Password
Any idea which configuration file I will need to update to get it work?
BTW I did not get any error during installation and configuration.
Regards,
Gaurav

Hi All,
I recently installed OIM 11.1.1.3 After installation when I try to search approval task, I am getting the following error:
<Warning> <oracle.iam.consoles.faces.mvc.common> <BEA-000000> <oracle.iam.platform.canonic.base.NoteException: An error occurred while searching tasks from the SOA Server.>
When I ran the check from Diagnostic Dashboard, I got the following result:
Test Name SOA-OIM Configuration Check.
Description Checks whether the details provided for SOA-wiring are valid or not.
Result Failed
Details
Invalid SOA parameters found in the configuration file of Oracle Identity Manager.
The following parameters are empty:
     RMI URL
     SOAP URL
     Weblogic Username
     Weblogic Password
Any idea which configuration file I will need to update to get it work?
BTW I did not get any error during installation and configuration.
Regards,
Gaurav

Where do we configure check register

Hi
while processing transaction FCHN, i have put a tick to "List of outstanding checks" still its showing all the checks which are cleared as well as outstanding, i hope there is some configuration missing
can anybody help me.

Hello,
There is no provision for configuring check register.
You can get the outstanding checks, provided if you have used FCHR to inform the system what checks are being cashed.
Used FCHR before FCHN.
Regards,
Ravi

How to check java disable

Hello Friends,
i have desktop application...
i am technically not that much experince..
i have one problem in my pc.
i don't know how to check java disable or not?
can any one guide me for the same
Thanks in advanced,
<Link Edited By Host>

The automatic disable is for Java (not javascript) INSIDE Safari.
Safari > Preferences > Security > [√] Enable Java
To check that Java is installed, open Java Preferences.app, available in your /Applications/Utilities folder
If Java is installed, it will show the version. If not Installed, you should be offered the option to download and Install it.
There is also a checkbox in Java Preferences for:
[√] Enable applet Plug-in and Web Start Applications (unchecked by default).
If you do not use Java inside your Browser for a few weeks, it will become disabled to protect against malware that downloads java.

Check for disabled cookies

I need to be able to check if cookies are enabled or disabled on the server side using JAVA. On the client side, it is easy to check for disabled cookies, but we need that functionality on the server side.

It is a though one and not very easily accomplished.
Conceptual idea on how to do it:
Server sends page to user and gives it an cookie.
The page contains generated unique URL's.
As soon as the user clicks on a link. Assemble information from the user by checking incoming cookie and the URL. If the cookie does not exist or does not conform to the one sent for the unique URL, user has them disabled or fooling them via proxy-server of some sort.
Voila - now you know if they got cookies enabled or not!
Don't think there is another way. Some web servers do this by automatic to keep track of sessions and some don't. Check manual for your server.
Pros:
Seamless transition for cookie based servers
Cons:
Strange URL's for the user
Might need URL rewriting for all code
User must traverse one way or another through 2 pages
Generated pages has to be used. Static HTML is a bit hard for this purpose.
Regards,
Peter Norell

Personas Configuration Check

I've recently upgraded to Personas 2.0 SP02 and I'm having some trouble getting the RFC destination required for the Configuration check tool to work.
When attempting to create the RFC destination (as detailed in this blog: Personas - Enabling Configuration Check of Target Systems), I'm receiving an HTTP 404 - Not Found error when testing the connection. I've validated the host and port # are correct and working since I can successfully test the restgui service. The logon procedure I'm using is an SAP RFC Logon and the user has SAP_ALL. I'm unsure of what else to check??
Any and all ideas are welcome.
Thanx in advance,
Elder

Thanx Thien, after using that prefix path value to test I was able to successfully test the RFC destination. So I removed the prefix path and saved my entry.
I ensured that the HTTP Connection value in the Maintain Systems configuration points to my new RFC Destination and it does. However, when I go to the Configuration Check tool I'm seeing "Unable to determine configuration" for the last 6 in the Target systems list. Please see the attached screen shot.
All the information I've found points to an incorrect RFC destination causing the message below, but that's obviously working fine. Any idea what else it may be?

Note 1749935 & DBACOCKPIT::SAP Configuration Check

Hi,
my box has got SAP_BASIS 16 on ASE 15.7.0.131, do I must check note number 1749935 (SYB: Configuration Guide for SAP ASE 15.7) or DBACOCKPIT::SAP Configuration Check is enough?
Thank you.

Hi Ganimede Dignan,
If my understanding is correct. Are you trying to configure the DBACOCKPIT
if Yes, use the SAP note 1539124 - SYB: Database Configuration for SAP applications on SAP ASE
Regards,
Ankitha

Configuration check printing

How can I configure Check printing process step by step in SAP FI.
Please tell me step by step,
Ragards,
Ananda

HI
No configuration required for Cheque printing....
we need to develop cheque printing format by using smartform or sapscript
Mahesh

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

Why is my Hardware Accelerate Composition, Layer, and Footage Panels check box disabled

Hello anyone!
I have all the requirements to meet Adobe's standards for GPU requirements, but this check box (Hardware Accelerate Composition, Layer, and Footage Panels)[Edit>Preferences>Display] is disabled for me, why? Do I need to worry about this setting? Does it really matter? Any information on this topic would be helpful. Thanks in adavance for your feedback.
GPU Information:
Fast Draft:
Available
Texture Memory:
924.00 MB
Ray-tracing:
GPU
OpenGL
Vendor:
NVIDIA Corporation
Device:
GeForce GTX 470/PCIe/SSE2
Version:
3.0.0
Total Memory:
1.20 GB
Shader Model:
4.0 or later
CUDA
Driver Version:
4.2
Devices:
1 (GeForce GTX 470)
Current Usable Memory:
608.00 MB (at application launch)
Maximum Usable Memory:
1.25 GB
Computer:
Windows 7 64bit SP1
24GB MEM
i7 intel
Feature support levels
There are three tiers or levels, from lowest to highest requirements, of support:
Level 1: For OpenGL SwapBuffer:
This level simply requires a GPU that can do OpenGL 1.5, or greater, with Shader Model 3.0, or greater. Most ATI and NVIDIA cards, and the Intel HD Graphics 3000 chipset (available in the MacBook Air, Mac Mini, various Windows machines, etc.) and 4000 (Windows only at this time) are supported. If your GPU does not support these requirements, software OS blitting like CS5.5 occurs, and there are improvements for software blitting in After Effects CS6, as well.
Level 2: For Fast Draft previews, Hardware BlitPipe, and Cartoon GPU acceleration:
Includes Level 1 features. This level requires OpenGL 2.0, or greater (with Shader Model 4.0, or greater, on Windows), and 256 MB, or greater, of texture memory. Most ATI and NVIDIA cards released in the past five years, plus the Intel HD Graphics 3000/4000, support this level.
If your GPU does not support these requirements, these features will be disabled:
Fast Draft mode
The "Hardware Accelerate Composition, Layer, and Footage Panels" preference.
The Cartoon effect's "Use OpenGL When Available" option (the Cartoon effect then runs on the CPU).
Level 3: For Ray-traced 3D rendering on the GPU:
Includes Level 1 & 2 features (for machines with attached monitors). This level requires a supported NVIDIA GPU and 512 MB, or greater, of texture memory. For a current list of supported GPUs, see the Adobe website.

Well, you should be concerned that it isn't available - there is still some configuration issue with your graphics card - but you can live without it most of the time.
Mylenium

Configure Check-In disabled

Similar Messages

Maybe you are looking for