Dit is een alinea. Een alinea is een eerste te leren element en vormt de basis van WordPress blogging. Het is belangrijk dit te leren kennen.
Dit is een tweede alinea.
Dit hoort nog bij de 2de alinea.
De derde alinea is een bullet list:
De vierde alinea is een numbered list:
Dit is de laatste alinea.
How to move the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component and how to fix the latter when it’s broken (SCCM 2012 R2)?
Attention: this blog post has been written based on SCCM 2012 R2, more precisely with SP1. There is a small chance that this article is not completely true for SCCM 2012 R2 without SP1 or even that the content lies quite far from reality in SCCM 2012 non-R2. What is certainly true is this post doesn’t apply for older SCCM versions (2007 and older) for at least a decent amount.
This blog post’s goal is twofold:
- Describing how to change the location of the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component. Please read the paragraph “How to change the location of the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file?” to deep-dive into this one.
- Describing how the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component may be broken, what happens then and how to fix it, even if you didn’t try to change the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file. See the paragraph “What if the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component is broken?” hereunder for that part.
In both cases it may be useful to start with the introduction paragraph “First some background information on SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component…” below. In the case of fixing a broken component (the 2nd goal of this post) I also think it’s worth reading the part about changing the location of the SMS_[SITESERVER-FQDN] folder and the smssqlbkup.log file, because it contains some in-depth details which may be useful to understand how to fix a broken SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component.
Read the rest of this entry »
There is a limit on the size of content (like files) one can upload when that content is hosted on an Internet Information Services (IIS) web server. The limits in charge depend on
- The version of IIS
- The configuration of IIS
The possible usage of certain ISAPI extensions and filters
- If so, which extensions/filters? (for example: ASP or ASP.NET)
- If so, which versions of extensions/filters (for example: version 4.0 of ASP.NET)
Different versions of IIS and ISAPI extensions/filters have different upload limit settings and/or hardcoded upload limits. Yes, you can already feel this article, that restricts itself to IIS, ASP and ASP.NET, won’t be THAT easy… 😉
Read the rest of this entry »
In System Center Updates Publisher (SCUP) 2011 there are some catalog references present by default, i.e. under “My Catalogs” in the pane “Catalogs”. If you select such a reference you can issue the command Import, which lets you import the catalog behind the reference, meaning the catalog is downloaded and the updates mentioned in the catalog are added to SCUP (well, actually the metadata of each of those updates is added). When added, you can view them in the pane “Updates” under “Overview”\”All Software Updates”\[NEW FOLDER FOR THE CATALOG’s UPDATES]. All this seems to work great, except for the catalog “Fujitsu PRIMERGY Updates Catalog” from publisher “Fujitsu Technology Solutions GmbH” (so from the company Fujitsu)… The catalog targets Fujitsu PRIMERGY servers. Read the rest of this entry »
As you all know, many versions and editions of Windows were developed and released over time. After a while it could be useful to have a list by hand that can give you a quick overview of those versions and editions. Below you find a table that lists every main Windows version. With “main” I don’t mean the most important versions; what I do mean, is I only list the distinct versions at “the highest versioning level”, but no sub-versions (versions that fall under the main version). For example, Windows 7 is listed, but I won’t talk about Windows 7 SP1 or some small update for Windows 7. Later on though I’ll mention one “smaller” update anyway, because it’s quite special, in the sense that it’s almost considered to be a main version, although officially it isn’t. Note I’m only dealing with “normal/classic” client and server flavors here, so I’m not talking about Windows Mobile, Windows Phone, Windows Embedded, etc. Read the rest of this entry »
Windows 8, Windows Server 2012 and many others: a complete and updated overview of their releases and related aspects
The last couple of days were quite busy: several Windows 8 SKUs, Windows Server 2012 SKUs and other products (like Visual Studio 2012 SKUs) have been released, while many others have been RTM’d (like Windows RT), gotten (new) public test releases (like Windows Server 2012 Essentials) and/or are expected to be released soon (like Windows Phone 8 SDK). I’ve already written 2 articles about it:
- “Windows 8, Windows Server 2012 and others RTM’d”: https://windoh.wordpress.com/2012/08/13/windows-8-windows-server-2012-and-others-rtmd
- “Windows 8 released”: https://windoh.wordpress.com/2012/08/15/windows-8-released
Now that we are a few more days full of news/releases/… further, things have become more clear and I’ve found a little bit more time, I thought it was time to write another article which is more complete and updated. So with the start of this new article my previous blog posts are already outdated and not-so-complete anymore. J Read the rest of this entry »
UPDATE: there is a new blog post which is more complete and updated. Check out https://windoh.wordpress.com/2012/08/26/windows-8-windows-server-2012-and-many-others-a-complete-and-updated-overview-of-their-releases-and-related-aspects.
On the 15th of August 2012 Windows 8 has been officially released, although only to a limited audience, i.e. MSDN and TechNet subscribers. Through TechNet 24 SKUs are available, while this is 36 at MSDN (the same 24 + 12 checked builds, used for debugging and typically only useful for a small group of developers).
The release isn’t exactly a surprise, as it was announced about 2 weeks ago. As you probably know Windows 8 and other products were RTM’d on the 1st of August 2012. It was also officially announced Volume License customers with Software Assurance (SA) may expect Windows 8 on the 16th of August 2012 UPDATE: through the Volume Licensing Service Center (VLSC) site. Other programs follow later, with General Availability (GA) planned for the 26th of October 2012.