I can't get ClearTeam Explorer to register a new license server. It keeps referring to the old one.
The error I get back when I try to connect is that it can't connect to LICENSE_HOST_X.
I've changed the setting in 'Home Base's control panel to point to the new LICENSE_HOST_Y, which works for the clearlicense tool and clearcase doctor but not for the team explorer.
The license settings are contained in the Windows Registry at HKLM\Software\Wow6432Node\Atria\ClearCase\CurrentVersion\Licensehost for Atria licenses.
For FlexNet licenses, the PortAtHost value at HKLM\Software\Wow6432Node\Rational Software\Licensing\8.0\ServerList comes into play as well.
The odds are VERY good that you're dealing with Windows registry virtualization. If you open the legacy "control panel" on Windows 10, run the "ClearCase" control panel as Administrator (or open "cc.cpl" from an elevated command prompt) and check the server information there. If you see different values for EXPLICITLY elevated and non-explicltly elevated control panel starts, you have entries in the "user specific" virtual registry store. Please note that this is a WINDOWS function, and not a ClearCase one.
Disabling the albd service on the license server is a very bad idea unless that is the only function the albd is providing. Disabling it on the client will essentially kill any local views AND the ability to map views to drives when the "credential manager" service that depends on this service fails to start.
Check if any of elements mentioned in "How to change the hostname in the IBM Rational ClearCase environment" might have an influence in your case.
IBM Rational ClearCase supports two types of licenses, the Rational Common Licensing (FlexLM) and the Classic Atria licensing.
Update these files with the new host name:
Rational common licensing (FlexLM):
/var/adm/rational/clearcase/config/flexlm_host
Rational ClearCase Classic/Atria licensing:
/var/adm/rational/clearcase/config/license_host
So it can help to know if the new license server is of a different nature than the old one.
At the client level:
UNIX/Linux clients:
Update the new registry server's host name in the file /var/adm/rational/clearcase/config/rgy_svr.conf
Update the License Server using the instructions in the server configuration guidelines.
Windows clients:
Update the new registry and license server hostname information using the IBM Rational ClearCase control panel located under the Windows control panel.
If nothing work, I would, if my client is on Windows, search for the old license server name in the Windows Registry, and replace or even delete those entries.
On Windows, the OP V.Bogd confirms in the comments:
The problem went away after I disabled an "Atria Location Broker" service.
That was the service needed, as seen in this thread, for the old license manager:
No license available from ClearCase license manager;
Use clearlicense to display license usage
You can see more on albd_server.exe here.
Related
I have a VirtualBox laboratory with a Windows Server 2019 machine and two Windows 10 machines. Each machine can ping the other ones and the Server machine is a Domain Controler. The clients are part of the domain that is labs.local. The Server has a static IP, and the IP of clients are given by the DHCP Server.
Then I built an Active Directory structure of OUs, users and groups. There are three independent OUs from each others. My goal is to deploy an MSI file only in one OU, lets say "IT". For that, I downloaded the MSI file and put it in a shared folder in the Server. I can access the shared folder from the clients by its UNC path with any user.
Now in Group Policy Management I created a new GPO and then I edited it. In the Group Policy Editor I chose User Configuration > Software Settings > Software Installation. Then I created a new assigned package with the UNC path of the MSI file. At the end I closed the Group Policy Editor and linked the GPO with the OU "IT".
However, after updating the group policies it seems that the GPO applies to the computer (Windows 10 machine) and not to the users because users from other OUs also have the MSI installed, in this case it's Firefox.
Can you give me a hint on how to deploy (and install) a MSI file only in a singles OU ? Thanks.
• Please check the ‘OU’ that you have applied the GPO to whether it has only computer systems or does it include users also. If it includes users also, then this group policy will be applied to the systems on which these users will be logged on to. This is the publishing method of installing a package in AD environment wherein the software package will be installed in those systems where the users in selected OUs have logged on to. This software package will be available in ‘Add or Remove Programs’ section of the control panel.
• Similarly, if the OU has computer systems only, and you have applied the GPO as specified in the question, then no computer system or user will be able to install that software package. And if the following GPO setting has been applied with users as well as computer systems in the OU, then when the user logs on to the computer, the software package gets installed and when the computer system starts, the software package gets installed. This is known as assigning method of software package deployment in AD environment.
‘ Group policy Management --> Select the GPO --> Edit --> Computer Configuration --> Software settings --> Software Installation --> New --> Package --> Type the UNC path of the share where the software package is placed --> Open --> Ok --> Save ’
Please find the below link for more information on the above topics: -
https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/use-group-policy-to-install-software
We have Clearcase version 9.x is running with Linux host. We have started experiencing the view disconnected issues on post-reboot of the user systems ( which are running with Windows pro 10 & windows ClearCase client 8.x). The view mapping drives show as disconnected and we need to re-map the view drives to fix it each time the system reboots. Some cases the view shortcut alone disconnected from the ClearCase explorer and we need to add the view shortcut again to map the drives. The default view drive M: shows, as disconnected in few systems, starting the ClearCase services and adding view shortcuts again, helps here. And few other systems with same configuration working fine without any issues.
I have a few questions on this,
Am I missing anything specific with Windows say like patching, Anti-virus etc
Is the issue exist & common with Windows 10 operating system
How the mapping issues can be fixed, I am looking for some solutions which can be tested
Kindly suggest if you come across this issues
Regarding the drive M:\, thus us directly linked to the ClearCase MVFS service: make sure the "Credentials Manager Service" service is set to run automatically
Check the MVFS (for ClearCase 9.0) is properly installed: that will enable the dynamic views.
Regarding the shortcuts, check "Mapping an automatic view root directory to a drive letter": they should be subst command, which you can make persistent across reboot
But if those subst involve dynamic views, then again, the MVFS service needs to be correctly started, or those drive letters won't show up.
This can happen if the albd is not started by the time the user logs in, this delays the start of the credential manager service. The fast-logon optimization can allow the user to in before services start.
If the views you're using are not local, you can decouple the credential manager service from its dependency on the albd service, and this could help.
( which are running with Windows pro 10 & windows clearcase client 8.x).
You need to upgrade to 9.0.1.x. ClearCase 8 has not been supported for (exactly) 2 years. If your hosts are running Windows 10/1909, you will need to update to 9.0.1.9 as that is the version that has been tested with 1909. Also, the MVFS "network provider" information does not survive a windows "feature update" install as that install is really a full OS install folloed by settings migrations, and MS's migration still leaves something to be desired.
You may want to do the upgrade via the "clean install" method of:
Uninstall ClearCase 8.0.x & reboot
Navigate to C:\ProgramData\IBM and remove the Rational.preserve* directories.
Navigate to \Windows\System32\Drivers and ensure that MVFS*.sys files are no longer present
Install ClearCase 9.0.1.9
ClearCase 9.0.1.8+ changed the MVFS from a 2-part (MVFS + MVFS Storage Filter) to a 1-part (MVFS only) driver configuration. We have seen reports of the old MVFS drivers not being completely removed on upgrade. In the worst cases, the old MVFS driver files were both present alongside the new MVFS driver, and all 3 were somehow loaded. This caused post-upgrade blue screens.
On my domain server 2012r2I am trying to deploying office 2007 but not all of the office I need to install only excel and word
I found an .msi file within the dvd installation and found many .msi packages
called ExcelMUI.msiand WordMUI.msi at directory
...\English\Excel.en-us\ExcelMUI.msi
...\English\Excel.en-us\WordMUI.msi
can I use them to deploy only excel and word through domain server 2012r2?
are they valid as .msi packages installer ?
Best Guess: I wonder if those MUI-setups are Multilingual User Interface setups. I think you should get on a virtual machine and try to run the setup.exe instead (if there is one) and then go to "Custom" or equivalent to see if you get a feature selection dialog. Then you should select Word and Excel to install fully and you can disable most other features (don't disable the shared features, just the other apps would be my suggestion - Outlook, PowerPoint, etc...). It is possible that those MSI files you mention can be used directly. You could try to run them - but only on a virtual of course. Or on a computer which does not matter - test computer of some sort. Look for a custom option and a feature dialog there too. Sorry, all I can suggest without installation media access.
Sure?: With all that said, Office on a domain server? Do you mean domain controller? (hope not). Sounds like a very dangerous move if you ask me - with all the security holes Office contains. At least make sure to run Windows Update or Office Update or whatever mechanism you have to deploy security fixes. Can I be curious and ask why the server needs Office? Is it for automation only?
Viewer for MSI Files: You can open and inspect MSI files using the free tools Orca, SuperOrca or InstEd (links towards bottom). I have an old answer on superuser showing how MSI features can be seen inside the MSI file.
While installing ClearCase Client I want to avoid providing clearcase_albd sevice account password to the developers.
Is there any way this can be done so that end-users need not know clearcase_albd password?
This is generally done launching a silent installation using a response file from a network share drive (ClearCase 7.1.x).
That shared drive is not accessible by the user, only by a special account that the support uses for the installation.
You find the same technique for ClearCase 8.x: "Installing ClearCase silently using a response file".
I used to install clearcase client on one particular windows domain and was ok. I want to install clearcase in different windows domain but it is not allowing me to map network drive. Do you know if this new domain will allow me to install cc client? One thing to remember: when type "net group /domain", no cc groups are found ....Is there a way to proceed there?
Thanks for any help !!
This is usually because the albd account user isn't allowed to map that new network drive.
See "Domain user and group accounts".
Plus, installing to a new Windows domain will have side effects on the existing ClearCase Views.