Jump to content

BSOD on Windows6.1 & ViPNet CSP 4.2.10

basid

By basid
in ViPNet CSP 4.х

 Share

Recommended Posts

basid

basid

Posted
Posted

Бету ViPNet (сейчас 4.2.10.51307) тестируют на Windows 7 x64?

Если на более ранних (4.2.5 - 4.2.9) отваливался системный (не ГОСТ-овый) TLS, то сейчас - BSOD после установке компонента совместимости с MS CryptoAPI.
Медленно и с трудом перезагружаемся, а потом - падаем.

К сожалению, дампа пока нет - на тестовой системе (сейчас) маленький раздел и система удаляет дамп памяти из-за нехватки места: 

<EventData>
  <Data Name="param1">0x000000f4 (0x0000000000000003, 0xfffffa80065984a0, 0xfffffa8006598780, 0xfffff80002bc3190)</Data>
  <!--Удалён системой из-за нехватки места: Data Name="param2">C:\Windows\MEMORY.DMP</Data -->
</EventData>
<!-- Ещё одно, возможно, связанное событие -->
<EventData>
  <Data Name="BugcheckCode">244</Data>
  <Data Name="BugcheckParameter1">0x3</Data>
  <Data Name="BugcheckParameter2">0xfffffa8006402b00</Data>
  <Data Name="BugcheckParameter3">0xfffffa8006402de0</Data>
  <Data Name="BugcheckParameter4">0xfffff800031b8190</Data>
  <Data Name="SleepInProgress">false</Data>
  <Data Name="PowerButtonTimestamp">0</Data>
</EventData>

Краткий отчёт по установленным обновлениям и программам: 

Image Version: 6.1.7601.23505
----------------------------------------------------------------------------------------------------- | --------- | ---------------
Package Identity                                                                                      | State     | Release Type
----------------------------------------------------------------------------------------------------- | --------- | ---------------
Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~6.1.7601.17514             | Installed | Language Pack
Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~amd64~~6.1.7601.17514                      | Installed | Feature Pack
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514                           | Installed | Foundation
Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0                | Installed | Update
Microsoft-Windows-IE-Hyphenation-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0                | Installed | Update
Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0                   | Installed | Update
Microsoft-Windows-IE-Spelling-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0                   | Installed | Update
Microsoft-Windows-InternetExplorer-LanguagePack~31bf3856ad364e35~amd64~ru-RU~11.2.9600.16428          | Installed | Update
Microsoft-Windows-InternetExplorer-Package-TopLevel~31bf3856ad364e35~amd64~~11.2.9600.16428           | Installed | Update
Microsoft-Windows-LocalPack-RU-Package~31bf3856ad364e35~amd64~~6.1.7600.16385                         | Installed | Local Pack
Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16492 | Installed | Update
Microsoft-Windows-RDP-WinIP-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16398                   | Installed | Update
Package_for_KB2574819~31bf3856ad364e35~amd64~~6.1.2.0                                                 | Installed | Update
Package_for_KB2685811~31bf3856ad364e35~amd64~~6.1.1.11                                                | Installed | Update
Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11                                                | Installed | Update
Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.7                                                 | Installed | Update
Package_for_KB3125574~31bf3856ad364e35~amd64~~6.1.4.4                                                 | Installed | Update
Package_for_KB3177467~31bf3856ad364e35~amd64~~6.1.1.1                                                 | Installed | Update
Package_for_KB4019990~31bf3856ad364e35~amd64~~6.1.1.2                                                 | Installed | Update
Package_for_KB4092946~31bf3856ad364e35~amd64~~11.2.1.0                                                | Installed | Security Update
Package_for_KB4095874~31bf3856ad364e35~amd64~~6.1.1.1                                                 | Installed | Update
Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514                                              | Installed | Update
Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514                                              | Installed | Service Pack
Package_for_KB982018~31bf3856ad364e35~amd64~~6.1.3.2                                                  | Installed | Update
Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24136.1.4                                          | Installed | Security Update
----------------------------------------------------------------------------------------------------- | --------- | ---------------

Installed programs
--------------------------------------|---------------------------------------------------------------|---------------
{09CCBE8E-B964-30EF-AE84-6537AB4197F9}  Microsoft .NET Framework 4.7.2                                  4.7.03062
{86A043D5-87F3-38E2-82BB-4B69A528CC3D}  Microsoft .NET Framework 4.7.2 (RUS)                            4.7.03062
{710f4c1c-cc18-4c49-8cbf-51240c89a1a2}  Microsoft Visual C++ 2005 Redistributable                       8.0.61001
{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}  Microsoft Visual C++ 2005 Redistributable (x64)                 8.0.61000
{5FCE6D76-F5DC-37AB-B2B8-22AB8CEDB1D4}  Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161  9.0.30729.6161
{9BE518E6-ECC6-35A9-88E4-87755C07200F}  Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161  9.0.30729.6161
{1D8E6291-B0D5-35EC-8441-6616F567A0F7}  Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219     10.0.40219
{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}  Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219     10.0.40219
{37B8F9C7-03FB-3253-8781-2517C99D7C00}  Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030   11.0.61030
{CF2BEA3C-26EA-32F8-AA9B-331F7E34BA97}  Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030      11.0.61030
{B175520C-86A2-35A7-8619-86DC379688B9}  Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030   11.0.61030
{BD95A8CD-1D9F-35AD-981A-3E7925026EBB}  Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030      11.0.61030
{929FBD26-9020-399B-9A7A-751D61F0B942}  Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005   12.0.21005
{A749D8E6-B613-3BE3-8F5F-045C84EBA29B}  Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005      12.0.21005
{F8CFEB22-A2E7-3971-9EDA-4B11EDEFC185}  Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005   12.0.21005
{13A4EE12-23EA-3371-91EE-EFB36DDFFF3E}  Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005      12.0.21005
{B13B3E11-1555-353F-A63A-8933EE104FBD}  Microsoft Visual C++ 2017 x64 Additional Runtime - 14.11.25325  14.11.25325
{B0037450-526D-3448-A370-CACBD87769A0}  Microsoft Visual C++ 2017 x64 Minimum Runtime - 14.11.25325     14.11.25325
{568CD07E-0824-3EEB-AEC1-8FD51F3C85CF}  Microsoft Visual C++ 2017 x86 Additional Runtime - 14.11.25325  14.11.25325
{029DA848-1A80-34D3-BFC1-A6447BFC8E7F}  Microsoft Visual C++ 2017 x86 Minimum Runtime - 14.11.25325     14.11.25325
{97599C5C-7F46-4083-980F-D96E97CCFDEC}  PDF-XChange Lite Home                                           7.0.325.0
{2454D077-3680-459F-AC33-F6973ABE4C2A}  Драйверы Рутокен                                 		4.3.02.0000
--------------------------------------|---------------------------------------------------------------|---------------

 

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

Поскольку это тестовая система, то:
1. Других криптопровайдеров нет;
2. Антивирусов - тоже нет. Только штатный антишпион, он же - "Защитник Windows".

Если на эту же тестовую систему установить (аналогично настроив) 32-разрядную семёрку, то:
1. ViPNet CSP работает;
2. Работает даже при наличии КриптоПро CSP. С поправкой на "поддержка MS CryptoAPI только для одного CSP".

Таким образом, проблема специфична именно для 64-разрядной Windows 7.
Что возвращает нас к исходному вопросу: бету ViPNet CSP тестируют на 64-разрядной Windows 7?

P.S.
На всякий случай, напомню: расширенная поддержка Windows 7 заканчивается в (ещё не близком) январе 2020 года.
И, на всякий другой случай, процитирую Microsoft Lifecycle Policy FAQ: "Extended Support will be available to all customers ... security updates at no additional cost".

Link to comment
Share on other sites
Wild

Wild

Posted
Posted

Поставил CSP 4.2 (10.51307) со всеми компонентами, на виртуалку с Win 7_x64 Sp1 максимальная, перезагрузился. Полет нормальный пол дня. Что я делаю не так?

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

Вот и мне хотелось бы понять, что я делаю не так.

Можно увидеть содержимое буфера из:

Цитата

dism -english -online -get-packages -format:table | clip

?

Link to comment
Share on other sites
Wild

Wild

Posted
Posted

Да не жалко.

2018-05-16 08:04:16, Info                  DISM   PID=2228 Scratch directory set to 'C:\Users\Admin\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2018-05-16 08:04:16, Info                  DISM   PID=2228 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadImageSession
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Manager: PID=2228 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM.EXE: 
2018-05-16 08:04:16, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2018-05-16 08:04:16, Info                  DISM   DISM.EXE: 
2018-05-16 08:04:16, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=4
2018-05-16 08:04:16, Info                  DISM   DISM.EXE: Executing command line: dism  -english -online -get-packages -format:table 
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Loading Provider from location C:\Windows\System32\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Connecting to the provider located at C:\Windows\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Getting Provider FolderManager - CDISMProviderStore::GetProvider
2018-05-16 08:04:16, Info                  DISM   DISM Provider Store: PID=2228 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Manager: PID=2228 Successfully loaded the ImageSession at "C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68" - CDISMManager::LoadImageSession
2018-05-16 08:04:17, Info                  DISM   DISM Image Session: PID=1344 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\OSProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:17, Info                  DISM   DISM OS Provider: PID=1344 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM OS Provider: PID=1344 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\LogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\PEProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Warning               DISM   DISM Provider Store: PID=1344 Failed to Load the provider: C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Manager: PID=2228 Image session successfully loaded from the temporary location: C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68 - CDISMManager::CreateImageSession
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider OSServices - CDISMProviderStore::GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-05-16 08:04:17, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-05-16 08:04:17, Info                  DISM   DISM.EXE: Target image information: OS Version=6.1.7601.17514, Image architecture=amd64
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:17, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:17, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-05-16 08:04:17, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-05-16 08:04:18, Info                  DISM   DISM Package Manager: PID=1344 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2018-05-16 08:04:18, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-05-16 08:04:18, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-05-16 08:04:18, Info                  DISM   DISM Package Manager: PID=1344 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2018-05-16 08:04:20, Info                  DISM   DISM Package Manager: PID=1344 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND
2018-05-16 08:04:20, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\pkgmgr.exe" : got STATUS_SUCCESS
2018-05-16 08:04:20, Info                  DISM   DISM OS Provider: PID=1344 Successfully loaded the hive. - CDISMOSServiceManager::DetermineBootDrive
2018-05-16 08:04:20, Info                  DISM   DISM Driver Manager: PID=1344 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Loading Provider from location C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Connecting to the provider located at C:\Users\Admin\AppData\Local\Temp\EF9C97E7-D701-4EA9-B5E3-3C1BEEB25D68\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider DISM Unattend Manager - CDISMProviderStore::GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
2018-05-16 08:04:20, Info                  DISM   DISM Transmog Provider: PID=1344 Current image session is [ONLINE] - CTransmogManager::GetMode
2018-05-16 08:04:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Provider Store: PID=1344 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2018-05-16 08:04:20, Info                  DISM   DISM Package Manager: PID=1344 Processing the top level command token(get-packages). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2018-05-16 08:04:20, Info                  DISM   DISM Package Manager: PID=1344 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-05-16 08:04:20, Info                  DISM   DISM Package Manager: PID=1344 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-Client-Refresh-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~6.1.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 with CBS state -17(CbsInstallStateSuperseded) being mapped to dism state 7(Unknown) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514 with CBS state -17(CbsInstallStateSuperseded) being mapped to dism state 7(Unknown) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Microsoft-Windows-LocalPack-RU-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.7 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Package_for_KB3033929~31bf3856ad364e35~amd64~~6.1.1.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Package_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Package_for_KB958488~31bf3856ad364e35~amd64~~6.2.7600.16513 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Package Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
2018-05-16 08:04:26, Info                  DISM   DISM Image Session: PID=1344 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Package Manager: PID=1344 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:26, Info                  DISM   DISM Provider Store: PID=1344 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:27, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-05-16 08:04:27, Info                  DISM   DISM.EXE: 
2018-05-16 08:04:27, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2018-05-16 08:04:27, Info                  DISM   DISM.EXE: 
2018-05-16 08:04:27, Info                  DISM   DISM Image Session: PID=2228 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2018-05-16 08:04:27, Info                  DISM   DISM Provider Store: PID=2228 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-05-16 08:04:27, Info                  DISM   DISM Provider Store: PID=2228 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-05-16 08:04:27, Info                  DISM   DISM Provider Store: PID=2228 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
 

Link to comment
Share on other sites
Wild

Wild

Posted
Posted


Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Packages listing:


------------------------------------------------------------------------------------------------- | ---------- | --------------- | ---------------
Package Identity                                                                                  | State      | Release Type    | Install Time   
------------------------------------------------------------------------------------------------- | ---------- | --------------- | ---------------
Microsoft-Windows-Client-Refresh-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~6.1.7601.17514 | Installed  | Language Pack   | 25.04.2018 5:44
Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~amd64~~6.1.7601.17514                  | Installed  | Feature Pack    | 21.11.2010 3:40
Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514                       | Installed  | Foundation      | 21.11.2010 3:40
Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514          | Superseded | Language Pack   | 21.11.2010 3:40
Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514               | Installed  | Feature Pack    | 21.11.2010 3:40
Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514   | Superseded | Language Pack   | 21.11.2010 3:40
Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514        | Installed  | Feature Pack    | 21.11.2010 3:40
Microsoft-Windows-LocalPack-RU-Package~31bf3856ad364e35~amd64~~6.1.7601.17514                     | Installed  | Local Pack      | 25.04.2018 5:44
Package_for_KB2999226~31bf3856ad364e35~amd64~~6.1.1.7                                             | Installed  | Update          | 15.05.2018 1:15
Package_for_KB3033929~31bf3856ad364e35~amd64~~6.1.1.1                                             | Installed  | Security Update | 11.05.2018 5:04
Package_for_KB3035131~31bf3856ad364e35~amd64~~6.1.1.1                                             | Installed  | Security Update | 11.05.2018 5:04
Package_for_KB958488~31bf3856ad364e35~amd64~~6.2.7600.16513                                       | Installed  | Update          | 11.05.2018 4:41
Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514                                          | Installed  | Update          | 21.11.2010 3:01

The operation completed successfully.
 

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

Спасибо, но уже разобрался: для 64-разрядной версии некорректно создаётся административная точка.
Обходное решение - не использовать административную точку для установки 64-разрядной версии.

Link to comment
Share on other sites
Vintik

Vintik

Posted
Posted
В 16.05.2018 в 15:49, basid сказал:

Спасибо, но уже разобрался: для 64-разрядной версии некорректно создаётся административная точка.
Обходное решение - не использовать административную точку для установки 64-разрядной версии.

Что это такое и где она отменяется?

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

Если вы не знаете, что это такое, то вам не требуется ничего отменять.

P.S.
Удобный, лично мне, вариант развёртывания msi-дистрибутивов.
Раньше я сталкивался только с маркетинговыми ограничениями фичи, теперь наткнулся и на техническое.

Link to comment
Share on other sites
Vintik

Vintik

Posted
Posted
3 часа назад, basid сказал:

Если вы не знаете, что это такое, то вам не требуется ничего отменять.

P.S.
Удобный, лично мне, вариант развёртывания msi-дистрибутивов.
Раньше я сталкивался только с маркетинговыми ограничениями фичи, теперь наткнулся и на техническое.

Неее - это не мой вариант! Я так не могу, если зацепило то теперь не отстану, лучше говорите по хорошему! А то начну звонить по ночам ))))))))))))))

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

msiexec -a дистрибутив.msi TARGETDIR="Полный\Путь"
В каталоге административной точки, в теории, будет создана распакованная версия дистрибутива с "минифицированным" msi-файлом.
Если к дистрибутиву прилагается msp (патч), то можно сделать:
msiexec -p исправление.msp -a мини.msi TARGETDIR="Каталог\Административной\Точки"

Удобно тем, что быстрее устанавливается, поскольку не требуется (отдельно) обновлять установку и антивирусу быстрее проверить отдельные файлы, чем мусолить большой пельмень.
Ну и кэш %SystemRoot%\Installer уменьшается в размерах.

Грабли:
1. Маркетинг - создание административной точки или осложнено или просто запрещено;
2. Есть дистрибутивы, для которых административная точка хоть и создаётся, но, в реальности не используется. Например - рантайм 2010-й ВидимоСтудии или NetFrawork-и;
3. Есть, как оказывается, дистрибутивы, которые неправильно создают административную точку. Пример пока один: 64-разрядная версия ViPNet CSP.

Примечания.
До установки собственно msi-дистрибутива могут делаться дополнительные шаги.
Если создаётся административная точка, то предварительные шаги должны делаться отдельно и самостоятельно.

Содержимое административной точки необходимо для восстановления установки или изменения состава её компонент.
Для обычного msi-дистрибутива тоже нужно, но, в этом случае "большой пельнень" будет взят из кэша.
Соответственно, если административная точка перемещается, требуется перекэшировать данные об установке:
msiexec -fv перемещённый.msi

P.S.
Малоизвестный факт: msi-дистрибутивы можно устанавливать с HTTP-сервера.
Чтобы это работало для административной точки, создавать её надо с добавлением свойства SHORTFILENAMES=1

Link to comment
Share on other sites
Vintik

Vintik

Posted
Posted

Ого - и откуда вы только всё это знаете. И если простыми словами то - получается просто каталог распаковки не делался? Так называемый ой самой точкой?

Спасибо.

Link to comment
Share on other sites
basid

basid

Posted
  • Author
Posted

Каталог - делается, но установка из этого каталога приводит к BSOD-у для 64-разрядной версии ViPNet CSP.
Если выполнить установку, не создавая административную точку, из исходной пары setupx64.msi и setup.cab - всё нормально.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept