If you get an HTTP 404 Error in a browser, after trying to access an IBM Connections Application and errors like
“File does not exist: E:/IBM/HTTPServer/htdocs/profiles”
start popping out in “error.log” file of the IBM HTTP Server, then most probably there is an issue with WAS Plugin.
I had this error just after the Installation of IBM Connections and the reason was the incorrect value of “WebSpherePluginConfig” variable, which contains the path to the “plugin-cfg.xml” file in the HTTP Server configuration. After the value was corrected and a correct path was supplied, IBM Connections could be accessed without any issue.
Some time ago we had a request from a customer to make sure that the incoming SMTP mails, for a specific internet domain, are routed only to users who have Internet Address with this exact internet domain set in their Person Document.
The Domino Router task behavior, at that point was the following (extremely simplified):
There was one Domino Global Domain document in the “names.nsf” with a lot of alternate internet domain aliases. So, this would mean that if the primary domain is “acme.com” and an alternate internet domain “acme-marketing.tv”, your users would be receive e-mails addressed with alternate domain even though they do not have it specified in their Domino Person document.
For one specific Internet Domain, this was not a way to go. The solution for this was quite simple, we needed to create a new Global Domain document with this Internet Domain specified as a Primary Internet Domain and remove the same domain from the first (“old”) Global Domain Document. This prevents the Domino Router task from looking up this Domain as Alias, thus making sure the E-Mails addressed with this domain are only routed to users who have this domain specified in their Person document.
After a new Global Domain document is created and you are satisfied with the config, restart the Domino Router task, to make sure that the change is picked up by the Router task.
This behavior is described, in detail, in the following article.
Two weeks ago, Benedek Menesi from Ytria held a cool Webcast about GDPR considerations in a Domino environment. This makes it clear that IBM Domino allows you to tackle a variety of challenges and GDPR is no exception.
You can watch the recording under the following URL:
If you are planning on changing the LTPA Token on a Sametime Community Server, save yourself a lot of pain by using the existing LTPA Document and keeping the default name “LtpaToken”. You may not get any errors on the console but the SSO using LTPA just won´t work.
If you want to enable Internet Sites on the Community Server, you should read the instructions in the following article:
Different backup strategy/software can lead to the need for changing the Transactional Logging style on a Domino Server. There are basically two possibilities for doing this.
Disable Transactional Logging on a Domino Server.
You should get a message: “Transactional logging being disabled after this restart”.
“NLOGASIO” or “LOGASIO” should not start.
Rename or delete the Transactional Logging directory.
Restart Domino Server to confirm there are no errors.
Enable Transactional Logging and set the Transactional Logging Style option you want.
Restart Domino and again confirm there are no errors on the console.
This is a subtler approach, although this takes a considerate amount of time, you can make sure there are no issues before letting your server back into production. You can also keep the old transactional logs if by renaming the Transactional Logging folder.
On the downside, a consistency check will be run on every database opened, for the first time, and a new DBIID will be assigned. This can take a lot of time depending on the size of your databases.
Change the Transactional Logging style.
Restart the Domino Server.
If you are changing from “Archive” to “Circular”, you can delete or move the old Transactional Logs.
After this, no consistency check or database fixup is will be done and the databases keep their old DBIID.
Here are some useful URLs about Transactional Logging:
Since about a week ago, there is a new DeskCenter Version, 10.6.4.2, it contains some Bugfixes and a few very interesting fixes.
A carbon copy can be applied and is displayed for emails which are send from the DeskCenter Helpdesk.
Tickets can be created automatically as recurrence tickets by a configured schedule.
Building blocks are available at many places in the Service Management to apply standardized text.
The options of ticket assignment to users or assets have been improved, e.g. the current DeskCenter user can be assigned to a ticket with one click. There are additional filter option to select the ticket assignee or assets.
The “last comment” can be used as variable in email templates for tickets.
On closing tickets, solutions approachs can be applied from existing Knowledge Base articles. The tickets can also be linked to the Knowledge Base article.
Software jobs can be initiated from a ticket for the assigned client computer.
The execution of quickscripts can be started from the ticket for users and assets.
A new function allows that the status of the ticket is automatically changed on sending ticket emails.
Tickets of the type “Problem” can be defined as “Known Error” or “Major Problem”.
Custom fields can be configured as mandatory fields for Helpdesk employees.
Single tickets can be linked.
Tickets can be hierarchically linked as master and sub-tickets in order to define dependencies between single tickets.
The system inventory was enhanced. Information about the build version for Windows 10 as well as the BitLocker status of disks is now available for the user.
The inventory of the Microsoft Office 365 portal was redesigned for the application of the new Microsoft Graph REST API. Further information from the portal is now available for the user, e.g. the user activities of Office 365 products, the user-specific activations on the user’s assets as well as an overview of the features which are enabled for the user in the licensed services.
Inventory Bug fix
The error handling at the inventory of the WMI classes was improved.
Knowledge Base New
The access on categories in the Knowledge Base and the included articles can be configured for single Helpdesk assignee groups.
License Management Bug fix
Hardware-based metric apply the correct inventory data for processors or cores respectively in specific product scenarios.
An error in the license calculation of hardware based metrics was solved. The number of physical or logical processors is now applied correctly at the calculation of processor and core metrics according to the respective client configuration.
License Management Change
The license metric “Microsoft per Core” has been consolidated with the other hardware-based metrics and is now calculated in “2 package” licenses.
OS Deployment New
The application of drivers in the PE can be configured by bulk edit.
Patch Management Bug fix
An error was fixed which occurred at the installation of Microsoft patches as MSI packages.
Progam Surface New
The Patch Level analysis which is based on the DNA Catalogue is now available for the user in the detail window for single clients.
Progam Surface Change
The performance to display the license menu was optimized. The user module of the SDI Agent displays the respective message if a reboot is pending.
Remote Management New
DeskCenter supports the application of the integrated Windows Remote Assistance to access remote clients.
Services and Communication New
Customized certificates can be configured for the DeskCenter services “Data Service” and “Worker Service”.
Software Deployment New
Multiple IP ranges can be configured for single DeskCenter software deployers.
The software actions “License Assignment” and “License Check” have been enhanced and allow to execute the respective action for multiple licenses.
A new software action checks if the system or the user is a member of a defined Active Directory group. It is possible to check security or distribution groups respectively.
Software rules can now be assigned to Active Directory groups.
A new software actions allows it to display messages in the user context at the clients via the SDI Agent.
Software Deployment Bug fix
An error was solved which caused that the IP ranges at the software deployer were not applied for the patch management.