Powershell SnapIns are not upgraded from PVS 7.15 LTSR CU3 to 7.15 LTSR CU4 after the upgrade is complete

Workaround:-

1. Mount the PVS 7.15 LTSR CU4 iso

2. Open the iso mounted and go to folder: Console > ISSetupPrerequisites.

3. You will see a list of Powershell snap-ins. Click on each of them and install one by one

– DelegatedAdmin_PowershellSnapin-x64

– ConfigurationLogging_PowershellSnapin_x64

– Host_PowershellSnapIn_x64

– Configuration_PowerShellSnapIn_x64

4. Now go to folder: Server > ISSetupPrerequisites.

5. You will again see a list of Powershell snap-ins. Click and install the following:- –Broker_PowershellSnapin_x64

6. Go to Programs and features and check: The snap-ins will be upgraded to CU4

Related:

  • No Related Posts

Unable to fetch AD User Groups

I need a solution

Hello,

After upgrade to the version 11.2.1 on the server 2012 R2 I get a error when I start the Symantec Endpoint Encryption Manager.

This is for all the snap-ins I added for SEE (see picture below).

In Windows I login as my admin account and for Symantec Manager whe have a default user.

With the previous version I had no error but under SEE Users and Computers I couldn’t see anything. 

I looked in a previous forum message and there was the solution to update Windows. I did that but nothing changed. Also looked at the server Roles Configuration, I use a default user and I am a member of Domain Admins

The strangest thing is that when my colleague (who installed the update and main enigineer) starts the programm he doesn’t have any errors en he can start the snap-ins.

0

Related:

  • No Related Posts

MMC cannot create the snap-in because of current user policy

I do not need a solution (just sharing information)

I was getting this error when after installing Endpoint Encryption 11.2 on a brand new server.  I got the error on the Software Setup and the Management password.

The problem is with Microsoft Management Console and requires a registry fix.

Make sure you export your registry before trying the following:

MMC Cannot create the snap-in because of current user policies.

         

1.         Start Registry Editor (regedit.exe).

2.         Move to HKEY_CURRENT_USERSoftwarePoliciesMicrosoftMMC

3.         Open the CLSID number giving the error

4  .      Double click RestrictToPermittedSnapins or something close to this

5.         Set to 0 and click OK

6.         Close the registry editor

0

Related:

  • No Related Posts

VNX: How to find the VNX/VNX2 Celerra CAVA Anti-Virus CIFS Microsoft Management Console MMC Snap-in

Article Number: 481008 Article Version: 4 Article Type: How To



VNX/VNXe Family,VNX1 Series,VNX2 Series,Celerra,vVNX Series,Unity Family

How to find the VNX Celerra CAVA CIFS Microsoft Management Console MMC Snap-in:

support.emc.com

-> Support by Products

-> VNX2 Series

-> VNX5600 or your VNX2 Series Model

-> Downloads

-> Product Tools

-> More

-> Search on the page for VNX FileCifsMgmt.exe 8.1.9.155


Another method to find the MMC Snap-in:

support.emc.com/search -> “virus” “VNX2 Series” -> second page –> its there…..


Here is a quick way to find the latest version of the VNX File Code:

support.emc.com

-> Support by Products

-> VNX2 Series

-> VNX5600 or your VNX2 Series Model

-> Downloads

-> More

-> More again

-> Search on the page for “dvd_image.iso”


The last method takes some time to find the latest version of the VNX File code.

Just by searching for “DVD IMAGE iso”, then search for the version number in of “All Support” for the related information

https://support.emc.com/search/?text=dvd%20image%20iso&product_id=36656&searchLang=en_US

As of today, May 17, 2016, the Latest VNX2 Series File Code version is 8.1.9.155, so search for “8.1.9.155”

https://support.emc.com/search/?text=8.1.9.155&product_id=36656&searchLang=en_US

Link to the latest the VNX Celerra CAVA CIFS Microsoft Management Console MMC Snap-in and install guide Plus the Latest VNX File code

VNX FileCifsMgmt.exe 8.1.9.155

https://download.emc.com/downloads/DL48750_VNX_FileCifsMgmt.exe_8.1.9.155.exe?source=OLS

This is a set of Windows-based tools that enable you to manage CIFS functionality in a VNX File, VNX Unified, or Celerra system. UNIX Attributes Migration, UNIX Users and UNIX Groups property page extensions, and UNIX User Management are used to manage users from Windows in native mode. …

March 10, 2016 | Celerra NS-120,Celerra NS-480,Celerra NS-960,Celerra NS-G2,Celerra NS-G8…More | DL48750 | Windows | 4.86 MB | Checksum 5a35508e9e55c2bb7c1b36a46e2638bd

Installing Management Applications on VNX for File 8.1

https://support.emc.com/docu48483_Installing_Management_Applications_on_VNX_for_File_8.1.pdf?language=en_US

… UNIX User Management Celerra AntiVirus Management is an MMC snap-in to the Unisphere.You can use the Celerra AntiVirus Management AntiVirus Management snap-in with the Common AntiVirus Agent (CAVA), third- party AntiVirus engines that run on a Windows NT or Windows 2000 or later, and a Data Mover to …

August 16, 2013 | VNX8000,VNX7600,VNX5800,VNX5600,VNX5400…More | docu48483 | Support Task:Administer, Configure, Install | 0.5 MB | pdf | en_US | Manual and Guides

8.1.9.155_dvd_image.iso

VNX2 OE for File OE 8.1.9.155 Upgrade DVD. Support use only for CLI code upgrades. Remote Support may ask customers to download this file in preparation for a remote upgrade. When upgrading a VNX2 File or Unified system, this code is to be used in with VNX OE for Block version 05.33.009.5.155. (CR52495)

March 10, 2016 | 1,198.0 MB | Checksum e164154061faf3ef47df40b67f9fd6cd

Related:

Software metering for Windows non-EXEs?

I need a solution

On Windows clients, is it possible to monitor and track usage of non-EXE’s?  I’m not finding much help in Symantec’s docs.

In my case, I’m thinking particularly for a vendor-specific MMC snap-in.  The snap-ins relies on the MMC.exe to run, but I want to know if <vendor>.msc is used.  

thanks!

Scott

0

Related:

7022145: Sentinel Agent Manager generates the error “Failed to connect to the database” and “The snap-in and the database must have the same version number” when launching console.

This document (7022145) is provided subject to the disclaimer at the end of this document.

Environment

Sentinel 7.1

Sentinel 7.3

Sentinel 7.3.2

Sentinel 7.4

Situation

When launching Sentinel Agent Manager console, the following errorsare generated:

Failed to connect to thedatabase on ‘<sqlserver>’. You do not have the appropriateaccess permissions to perform this operation. Please contact yoursystem administrator for more information.
Details:
0x80070005: Access isdenied
The snap-in and thedatabase must have the same version number. Snap-ins will not beadded.
Details:
You attempted to connectdiffering versions of a snap-in (version 7.3) and a database(version ). You must upgrade either the Agent Manager Servicedatabase or the snap-in for the connection to work.

Resolution

Verify that the SQL server configured for use with Sentinel AgentManager is online and that the SQL Server service is started.

Cause

If the SQL server is not online or visible on the network thenthese messages will be generated.

If the SQL server is online and the SQL Server service is notstarted, these messages will be generated.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7021792: Disabling EXTRA! Productivity Features using Windows Group Policy

The next section describes disabling productivity features using Windows Group Policy, which takes precedence over other methods. Note: For information on controlling EXTRA! productivity features using other methods (session files, template default files, security options, registry settings, Custom Installation Wizard, and/or MSI deployment), see Technical Note 2140.

Disabling Productivity Features using Windows Group Policy

To disable EXTRA! productivity features using Group Policy, complete the following tasks:

I. Modify Existing Host Session Files

Before disabling the productivity features using Windows Group Policy, modify your EXTRA! host session profile files (*.edp) to disable productivity features. Note: If you skip this task (later open a host session with productivity settings enabled after disabling them in Group Policy), the EXTRA! application may terminate ungracefully.

To modify each session file, complete the following steps:

  1. In EXTRA! X-treme, open the session file (*.edp).
  2. Click Options > Settings.
  3. In the Category list, select Productivity.
  4. Clear the checkboxes for the productivity features:
– Enable Productivity Pane

– Enable Spell Checking

– Enable Auto Complete

– Enable Auto Expand
  1. Save the session file.

When finished modifying session files, exit the EXTRA! application.

II. Copy the Administrative Policy Template File

Use the following steps to locate and copy the EXTRA! administrative policy template file (*.adm):

  1. Locate the EXTRA!.adm file for your language. After running the downloaded product to extract files (or inserting the CD media), the default folder for the English file is as follows.
    • Version 9.1:C:~AttachmateEXTRA!-v9.1.0admENU
    • Version 9.0 Service Pack 2:C:Documents and Settings<user name>Local SettingsTempEXTRA!-v9.0.2-spadmENU
    • Version 9.0 Service Pack 1:C:attachmate_tempEXTRA!-v9.0.1-spadmENU
    • Version 9.0: Use the file provided with later versions
    • Version 8.0: On CD 1, EXTRA!admENU
  1. Run RegEdit to open the registry key HKEY_CURRENT_USERSoftwareAttachmateEXTRA!WorkStationUserPreferences and examine the DirADMOpen value. Typically, this value is one of the following:
C:Documents and Settings<user name>My DocumentsAttachmateEXTRA!SchemesENU
-or-
C:Program FilesAttachmateEXTRA!SchemesENU
  1. Copy the EXTRA!.adm file from the folder found in step 1 to the destination found in step 2.

III. Edit the Group Policy

Use the following steps to edit Group Policy on Windows XP, Windows Server 2003, or Windows 2000.

  1. Start the Microsoft Management Console:
    1. Click Start > Run.
    2. Enter MMC and click OK. Tip: If you enter gpedit.msc instead, you can skip to step 3 below.
  2. Add the Group Policy snap-in:
    1. Click File > Add/Remove Snap-in.
    2. In the Add/Remove Snap-in dialog box, click Add.
    3. In the Add Standalone Snap-in dialog box, scroll down and select Group Policy.
    4. Click Add.
    5. In the Select Group Policy Object wizard, the Group Policy Object is Local Computer by default. Click Finish.
    6. Click Close and OK to close dialogs.
  3. Add the EXTRA! policy template file:
    1. Open Computer Configuration or User Configuration.
    2. Right-click Administrative Templates and click All Tasks > Add/Remove Templates.
    3. In the Add/Remove Templates dialog, click Add.
    4. Select the EXTRA!.adm file in the Schemes language subfolder (the copy destination from step II.3 above).
    5. Click Close.
  4. Disable the EXTRA! productivity features:
    1. Under Administrative Templates, open Attachmate > EXTRA! X-treme.
    2. Set the following properties to Enabled:
– View > Disable the View menu’s Productivity Pane option

– Options > Hide the Productivity brand of the Options Settings treeview

– Productivity Bar > Disable the Productivity Bar’s History option

– Productivity Bar > Disable the Productivity Bar’s Recent Typing option

– Productivity Bar > Disable the Productivity Bar’s Scratch Pad option

– Productivity Bar > Disable the Productivity Bar’s Macro Bar option

– Productivity Bar > Disable the Productivity Bar’s Office option
  1. Exit MMC or the Group Policy Object Editor to ensure changes are saved.

IV. Activate the Group Policy

Make the new Group Policy active by doing one of the following:

  • Restart the system, or
  • Click Start > Run and enter gpupdate /force (Note: This is a Windows command to refresh Group Policy settings; the /force switch option reapplies all settings.)

Open a host session in EXTRA! and verify productivity features are disabled as desired.

Related:

Citrix App Layering – User Layer Error “We were unable to attach your User Layer”

App Layering uses the file share path configured in the ELM management console to set registry keys in published images, which tell those images where to look for their user layers and elastic assignments. These registry keys are set at the time of publishing, so if the path has changed since the last time the image was published, the values will no longer align.

First, check in the ELM Management console to confirm the current file share location. Go to System->Storage Locations

User-added image

Now, make sure the highlighted file share location is the same as the registry key set on the published image where we saw the error. Open RegEdit, and navigate to HKLMSoftwareUnideskULayer and check the “RepositoryPath” key

User-added image

Finally, make sure that you are able to navigate to that directory on your virtual machine. Open up file explorer and check. If you do not have the correct share permissions, please refer to this article for additional configuration assistance: https://www.unidesk.com/support/learn/4.3.0/ms_hyper-v/itoc_2_layer_hv4/layer_user_enable_co_hv

User-added image

Related:

Re: Unity – Protect access to C$

This one’s easy. Any windows server always has these default administratively hidden shares too c$ d$, etc. So does VNX. By default the only users that will ever have access to this share are those that are in the local administrators group of the NAS server (or windows server BTW) in question. If you try via a computer management MMC, you can’t even change the access rights to the c$ share, you get a pop-up saying that:

“This has been shared for administrative purposes. The share permissions and file security cannot be set.”

Which is fine, it’s not a risk as long as you’re careful about whom you let be a local admin. This is by default, only domain admins, and perhaps the user who actually joined the NAS server to Active Directory in the first place.

Hope this helps,

~Chris Klosterman

Principal SE, Datadobi

chris.klosterman@datadobi.com

Related:

Event ID 10111 — Listener Availability

Event ID 10111 — Listener Availability

Updated: August 5, 2011

Applies To: Windows Server 2008 R2

The Listener is a component of the WinRM service that indicates to the service which IP addresses and ports to listen on for WS-Management related requests. Users can create one or more listeners.

Event Details

Product: Windows Operating System
ID: 10111
Source: Microsoft-Windows-WinRM
Version: 6.1
Symbolic Name: LOG_WSMAN_LOGON_OFFLINE
Message: User authentication using Basic authentication scheme failed. Additional Data Unexpected error received from LogonUser %1: %%%1.

Resolve
Restart the WinRM service

To restart the WinRM service by using the Services MMC snap-in:

  1. Click the Start button.
  2. Click Control Panel.
  3. Click System and Maintenance.
  4. Click Administrative Tools.
  5. Click Services to start the Services Microsoft Management Console (MMC) snap-in.
  6. Search for Windows Remote Management (WS-Management) in the list of service names displayed by the Services MMC snap-in.
  7. Right-click the Windows Remote Management (WS-Management) service name and select Restart to restart the service.

Note: If the WinRM service is not started, the Restart option will not appear in the context menu displayed in Step 7. In this case, select Start.

To restart the WinRM service by using a command-line tool:

  1. Type net stop winrm.
  2. Type net start winrm.

Verify

Use the winrm command line tool to create a request to the WinRM service to verify that the service is listening on the network.

To make a request, type winrm get winrm/config -r:<computer>, where computer is the name of the remote computer where the winrm service is running.

Related Management Information

Listener Availability

Management Infrastructure

Related: