Network professional? I'm sure I'm not, but I'm sure you'll find some hints about useful tools. Or maybe you just want to use a SSH service as proxy, tunnel.
HTML5, CMS, CSS and respsonsive are all unfamiliar terms? Then this is the right place for you, I am not a webprofessional, but I can give some start tips to the newbies.
With over 80% market share, Windows is the world's leading operating system. Tips & tricks, tutorials, troubleshooting and much more can be found in this section.
I’m a big WordPress fan! The community is huge, it has lots of plugins and it is very user friendly. Compared to a CMS like Typo3, simple end users can manage WordPress very easily and create posts, as well as customize pages.
This post shows some of my favorite addins and explains their function:
Secret Content– hide content from non logged in visitors
Post Expirator– The Post Expirator plugin allows the user to set expiration dates for both posts and pages.
NextGEN Gallery– The most popular gallery plugin for WordPress and one of the most popular plugins of all time with over 24 million downloads.
Members – Members is a plugin that extends your control over your blog. It’s a user, role, and capability editor plugin that was created to make WordPress a more powerful CMS.
During the migration from Server 2008 R2 – Citrix 6.5 to Server 2016 Citrix 7.15, the customer had a special request: that the language settings, printer mappings and Outlook shared mailboxes be transferred to the new Server2016/Office 2016 environment. Of course, we don’t want to copy the full Windowsprofile, instead we want only use the most necessary settings to keep the new profile as clean as possible. With the printer mappings and language settings there are so far no problems, all this can be found “relatively simply” in the Registry and taken over (Powershell is your friend).
With the Outlook shared mailboxes it was more complicated…we had in this specific case no possibility to get the relation between the assigned shared mailboxes and the users trough Exchange…the Exchange admin told us that you can’t read the relations with the current Exchangeserver settings.
Although you can technically read the members of a shared mailbox with get-mailbox or a similar command.
Probably you could also mount the shared mailboxes automatically to Outlook…if you like…but honestly, that’s not the point. And i’m not an MS-Exchange professional…😉
You can actually get Outlook profiles/mounted shared mailbox (profiles can be seen under CMD: “c:\Windows\SysWOW64\control.exe mlcfg32.cpl“)from the user registry. It may not be the best way but it works and offers a small advantage. You migrate only those shared mailboxes which the user has assigned to himself in the current Outlook version. You will not randomly migrate all shared mailboxes to the new Outlook environment just because the user is a member of those.
To cut a long story short… What needs to be done now to migrate the mounted mailboxes/profiles from Office 2010/Server2008R2 to Office2016/Server2016? First an export of the Outlook profiles: HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
Watch your step! This cannot be imported easily…because the path has changed ( Thank you Microsoft!).
New path under Office 2016 (Import to these location): HKCU\SOFTWARE\Microsoft\Office\16.0\Outlook\Profiles
There are a lot of cryptic registry keys but so far the migration and the Outlookprofiles hasn’t caused any problems. Write me in the comments, if you know the specific key’s which are needed to migrate shared mailboxes (so I can make everything a less streamlined and cleaner)…I don’t take this trouble today 🙂
You have to define the $root variable, it can be something like ‘$root = “$env:appdata\Profilmigration7x”‘ or a Network share. If you use the Appdata path, ensure to Copy the data to the “NEW” appdata-path if you use Citrix or another UPM versioning tool.
The IIS settings will be not saved. For example, IIS bindings to the default web site or HTTP Redirect entries that were made, will not be imported when you restore the backup ZipFile.
You can also take an IIS Configuration Backup.
Unfortunately, not all settings will be exported from the IIS here either… Therefore I recommend to make a backup of the server (VM Snapshot or similar) another method is to keep an installation documentation about the manual IIS configuration and to recheck the config after a configrestore.
One of my favorite editors for editing Powershell scripts is Visual Studio Code. Mircosoft’s OpenSource Code Editor, launched in 2016, is a wonderful editor and the biggest advantage is that it works on Windows, Linux and Mac.
In this article I want to show some advantages why I prefer this editor to the classic Powershell_Ise, Atom Editor and Notepad++. I also show useful addons and editor settings.
Okay first of all i’ll show you why
At the beginning I will show you the advantages of the editor:
The editor is very fast (no lags) and it starts very fast
The editor is with approx. 180MB installation size relatively slim in contrast to Visual Studio
The editor supports various programming and scripting languages, which can be installed using extensions.
Many Addons/Extensions (Debugger, DebugConsole, ColorEditors, Autocorrection, Sourcecontrol, GIT, TFS Server, Docker, various Azure Tools and Connections)
Code can be executed within the editor.
Integrated Terminal Console
Many configuration options (autosave, color selection, editor behavior, code arrangement and much more).
Command Explorer
Various color themes for the editor itself (dark / light, much based on Visual Studio)
Configuration can be easily done using .json files or GUI
Has a very large user community and is strongly pushed by Microsoft.
Distinctive differences to Visual Studio Editor:
Visual Studio Code organizes itself according to folder structures (file system) and not like Visual Studio with “Projects”
No integrated editor for Windows WPF/Windows Form GUI’s.
No Enterprise Debugging (CPU Runtime)
Those are my prefferd Custom Settings:
I have made the following setting in the JSON file (User Settings) to make the scripten more pleasant.
Two days ago I received the mail below. TLS-SNI-01 will no longer be supported in the future. With this guide I’ll show you how to update the Let’s Encrypt certificate to the new standards. In my concrete example it is a Debian System 9.7 (Stretch) with a Nextcloud (Apache webserver) and certbot.
Your Let’s Encrypt client used ACME TLS-SNI-01 domain validation to issue a certificate in the past 60 days. Below is a list of names and IP addresses validated (max of one per account):
************
TLS-SNI-01 validation is reaching end-of-life. It will stop working temporarily on February 13th, 2019, and permanently on March 13th, 2019. Any certificates issued before then will continue to work for 90 days after their issuance date.
You need to update your ACME client to use an alternative validation method (HTTP-01, DNS-01 or TLS-ALPN-01) before this date or your certificate renewals will break and existing certificates will start to expire.
First of all ensure you have certbot version 0.28.0 oder newer installed. Ensure your usig those comnmands with the root/admin user.