DELL-Vibha G's Posts

DELL-Vibha G's Posts

Presently only Dell Client Enterprise systems (  OptiPlex, Latitude, Venue etc.) are supported. Thanks Vibha
Hello Dharmesh,  Instead of installing VC++ runtime separately , you can copy msvcp100.dll, msvcr100.dll from VC2010 and msvcp110.dll, msvcr110.dll, vccorlib110.dll from VC2012 in the same folder... See more...
Hello Dharmesh,  Instead of installing VC++ runtime separately , you can copy msvcp100.dll, msvcr100.dll from VC2010 and msvcp110.dll, msvcr110.dll, vccorlib110.dll from VC2012 in the same folder as provider module. -Vibha  
VC++ 2010 and VC ++ 2012 both runtime are required on target machines for DellBIOSProvider v1.0 execution. There is no work-around. We will consider the issue  in next release which is work in prog... See more...
VC++ 2010 and VC ++ 2012 both runtime are required on target machines for DellBIOSProvider v1.0 execution. There is no work-around. We will consider the issue  in next release which is work in progress. Thanks Vibha
Looks that required WMI-ACPI support is not available in BIOS. Please send the model number and BIOS version of your computer to verify. You can check here if your platform and BIOS is in the suppo... See more...
Looks that required WMI-ACPI support is not available in BIOS. Please send the model number and BIOS version of your computer to verify. You can check here if your platform and BIOS is in the supported list  - http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11653.supported-platformsbios-reference-list-for-dell-command-powershell-provider BIOS upgrade may be required in your platform to execute DellBIOSprovider. Thanks Vibha
Please retry to load module with - import-module .\DellBIOSProvider.psd1 -Force -verbose Send us the screenshot of the verbose messages if DellSmbios: drive is still not available. Thanks Vib... See more...
Please retry to load module with - import-module .\DellBIOSProvider.psd1 -Force -verbose Send us the screenshot of the verbose messages if DellSmbios: drive is still not available. Thanks Vibha
Is the provider loaded and DellSmbios: drive available in your PowerShell session?   You can check by executiong the cmdlets Get-Module and Get-PSDrive.  dcdbas64.sys is not required for 1.0 rele... See more...
Is the provider loaded and DellSmbios: drive available in your PowerShell session?   You can check by executiong the cmdlets Get-Module and Get-PSDrive.  dcdbas64.sys is not required for 1.0 release of Dell Client Power Shell Provider. Thanks Vibha
For logging, option --logfile=<filename> is available to be appended in a DCC command. For example, CCTK.exe -i=inifile.ini --logfile=log.txt Please check if it helps in your use-case. Websit... See more...
For logging, option --logfile=<filename> is available to be appended in a DCC command. For example, CCTK.exe -i=inifile.ini --logfile=log.txt Please check if it helps in your use-case. Website for the last release DCC 3.1 is - http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7532.dell-command-configure               For the issue that occurs after ADK upgrade in WinPE, we would like to have more details. Thanks Vibha
The “UEFI” boot option, shows the available UEFI boot paths (vs. boot devices in "Legacy" boot option). UEFI boot is not intended to be a device-specific boot, and thus there is no default list of UE... See more...
The “UEFI” boot option, shows the available UEFI boot paths (vs. boot devices in "Legacy" boot option). UEFI boot is not intended to be a device-specific boot, and thus there is no default list of UEFI boot paths. UEFI boot paths only appear if manually setup or pre-defined boot paths are found. In F2 setup utility, a user can create a boot path by  “Add Boot Option” then entering the “Boot Option Name”, “File System List”, and “File Name” . Please note that UEFI boot paths are highly dependent upon how the user may have named them. There is a Whitepaper "UEFI on Dell BizClient platforms" available that can be helpful - http://en.community.dell.com/techcenter/extras/m/white_papers/20278835?~aj=true Thanks Vibha
It's WMI and SNMP with DCM. A whitepaper is available on OME and DCM integration - en.community.dell.com/.../20218168 Not sure about OMSA. -Vibha
There is no Nagios plug-in available for Dell | Command Monitor (DCM). DCM can be interfaced with OpenManage Essentials (OME) to manage Precision units. Thanks Vibha
The "SUCCESS" message is written to the console , hence cannot be redirected. Probably, in next release, we will send the console messages to PowerShell pipeline. Thanks for using DCPP and your fee... See more...
The "SUCCESS" message is written to the console , hence cannot be redirected. Probably, in next release, we will send the console messages to PowerShell pipeline. Thanks for using DCPP and your feedback. Vibha
Need to identify the attribute that caused the exception. Next attribute in SystemInformation category is OwnershipTag.  Please send us the output of  - Get-ChildItem DellSMBIOS:\SystemInformation\... See more...
Need to identify the attribute that caused the exception. Next attribute in SystemInformation category is OwnershipTag.  Please send us the output of  - Get-ChildItem DellSMBIOS:\SystemInformation\AssetTag -verbose Get-ChildItem DellSMBIOS:\SystemInformation\OwnershipTag -verbose Thanks for reporting the issue. We'll try to reproduce it at our end and get back. -Vibha
Please check the User's guide of newly launched 1.0 release - http://www.dell.com/support/home/us/en/19/product-support/product/dell-command-powershell-provider-v1.0/manuals Section 5 is ab... See more...
Please check the User's guide of newly launched 1.0 release - http://www.dell.com/support/home/us/en/19/product-support/product/dell-command-powershell-provider-v1.0/manuals Section 5 is about setting up the DellBIOSProvider in Win PE environment. Thanks Vibha
Thanks for the feedback. The error appears because this release does not support updatable or online help for the DellBIOSProvider module. Thanks, Vibha
This is work in progress. Cannot say at the moment if WinPE support will be part of the next release. Thanks Vibha
We need to check the functionality with TPM Activation. If the issue is found, it will be fixed in next release of DellBIOSProvider. Thanks for sharing the result with CCTK. -Vibha
There is a script available that might help you: Check if a BIOS password is set Please try it out and let us know how it goes. Thanks for contacting us Vibha
There are a few such issues in DellBIOSProvider. In next release, all of those will be fixed. Thanks Vibha
The issue is with Bootsequence setting on pure legacy desktops. We are aware of the issue and it is planned to be fixed in the next release.  Meanwhile, you can use CCTK CLI tool to perform the opera... See more...
The issue is with Bootsequence setting on pure legacy desktops. We are aware of the issue and it is planned to be fixed in the next release.  Meanwhile, you can use CCTK CLI tool to perform the operations with Bootsequence. Sorry for the inconvenience. Thanks for contacting us. Vibha
Thanks DAOV for sharing the feedback and using the DellBIOSProvider. Work towards the next release of DellBIOSProvider is in progress and a formal documentation would definitely be part of that. Fo... See more...
Thanks DAOV for sharing the feedback and using the DellBIOSProvider. Work towards the next release of DellBIOSProvider is in progress and a formal documentation would definitely be part of that. For MEBxHotkey and VTforDirectIO issue, we will check it and get back. Meanwhile please provide the BIOS version of your OptiPlex 9020 and result of the same operation with CCTK. We would like to hear more about the WinPE use case where you actually used the DellBIOSProvider. Thanks Vibha