Hello and welcome to IDERI blog!
Here you will find a continuously growing number of information about products like DSM, NetInstall, IDERI note, as well as HowTo’s, tips and tricks, announcements, offers, etc.
Our intention is to share our knowledge and experience in NetInstall and DSM with you so you can maybe find solme info that helps you to the work with the program. For this purpose know-how and instructions can be found here, written by NetInstall professionals of the first hour as well as tips and experiences of DSM / NetInstall beginners. This creates a mix of professional and beginner knowledge, from which everyone can learn something or use it as a reference work.
A new IDERI note release is now available.
The following features are included in the new IDERI note 3.2 Release:
- IDERI note Hotkey Support
- Creating, updating, deleting messages via hotkeys
- Usage of hotkeys on the logon screen
IDERI note 3.1 is out now!
The newest release of IDERI note features the following innovations:
With the lates release of IDERI note Version 3.0 we implemented some exciting and long awaited features.
Since IDERI note version 2.11 the IDERI note Client is started by the new clientlaunch.exe which derives its start parameters from a central value in the registry. This value is called “DefaultCommandLine” and located in the inotecln key in registry.
As there are scenarios where a computer has to start multiple IDERI note Client instances to connect to different servers this was done before with this (link) method. But today i want to show you how you can realize this behavior using the clientlaunch.exe.
With IDERI note, you protect your logged-in users in a targeted, timely manner and, above all, at the time of event validity. The message can be displayed via a simple popup or via a ticker directly on the user’s desktop. Pre-defined messages can be sent immediately with a push of a button in dangerous situations.
Of course, you can also use IDERI note <! – more -> as a general information system e.g. for cases of maintenance, system outages and more. This will reduce the internal e-mail flood and ensure that only the currently logged in users are aware of the current events. Users who are on vacation, sick, working shifts or maternity protection are not confronted with unnecessary emails. The IT department will be relieved as far as possible and the milestone for the essentials has been set.
For further details, you can find some other articles in our blog. As an alternative you can also visit our Youtube channel.
In this blog post we explain how to configure multiple names for a MS Windows server. “This works from Windows Server 2003”.
For this example we use a windows server 2012R2.
The server goes by the name ID-DC01 and should also be given the name IDERINOTE.
For this we first have to create the following registry keys on our server ID-DC01:
Eventhough IDERI note does not offer a timer to automatically resend messages at a certain time, this can be done with simple windows tools.
Let’s assume that every day at 5 o’clock we perform a restart of our servers. But since we have a small field office abroad, as well as some nocturnal employees or even colleagues working night shift in the company, who access some of the servers, we want to inform them now briefly with IDERI note about the upcoming restart of the server.
For the implementation, you only need a computer that is still running at this time, so preferably a Windows server, as well as the IDERI note Commandline Tools.
Every now and then the directory of a software still exists in e.g. C: Program Files (x86) after uninstallation. So how can you delete this most effectively?
To remove directories the command “Remove Dir” is available. However, you must make shure that the target directory is actually empty.
Therefore, please note that the target directory should be completely cleared by a “Delete”. Again, you have to be careful because the “Delete” command by default is not flagged. Do this by manually flagging the command from “Computer Related” to “Service Executed”. Otherwise, all files will remain in the directory, because a standard user in ProgramFilesDir usually has no write permissions. In addition, a little tip: Use the DSM variable %ProgramFilesDir% as an alias for “C: Program Files (x86)”. This will avoid unnecessary complications.
The script than should look like this (example):
With this all files in the target directory are generally deleted and removed by “RemoveDir” properly.