I’ve been running Napp-IT for a couple of years for my photo’s and other important stuff. My drives are a couple of years old so it was really time to upgrade from a 2 TB 3-way mirror to a 4 TB 2-way mirror.
These are the steps I took to accomplish this.
After an intense year of non-stop studying I treated myself to a new mediaplayer. After some research I decided to go with a NUC, an Intel NUC5CPYH to be more specific.
I’ll do a quick write-up of the installation and my experience with the device up till now.
Changing jobs and some other projects have kept from writing but I found a little time to write about a cool re-purpose project I’ve been working on.
This article has been sitting iny my drafts for almost a year. I wanted to delete it but Paul from Tinktertry talked me into publishing it any way even for historic purposes.
My homeserver had been passed its prime for some time now. So it was time to build something new. This is not a lab machine but something that will be running 24×7.
I didn’t want to spend money on an expensive NAS like a Synology, Thecus or QNAP so a plan was hatched to build an allround all-in-one virtualization beast.
Had to grapple with a tricky problem today. A user was getting this error message when trying to start application BLA_BLA_01:
“The system cannot find the specified path”
Error code xxxxxx-xxxxxx82C-00000003. This was odd because this had been a working package up till now…
A quick heads-up for SCCM admins. I came across this nasty issue and together with a colleague we quickly resolved this issue before matters got worse.
Since the answer cannot be found on the Microsoft Support site at the time of writing, you can find it here.
Just a quick heads-up for people using App-V in their environment and may have missed this:
The Fanastic Four: Falko Gräfe, Nicke Källén, Kalle Saunamäki and Ment van der Plas have joined forces to bring us a free App-V book!
I came across this error in a Mixed 4.0 / 4.5 MPS Farm. The users would try to access the 4.5 server (which was the only 4.5 server in the farm) and they would receive this error message.
The complete error was:
The Citrix servers reported that they are too busy to provide access to the selected resource. This message was reported from the XML Service at address http://someotherserver:80 [com.citrix.xml.NFuseProtocol.RequestAddress].
So what can we do about this error?
I’ve been busy rebuilding my home environment.
(articles will follow as soon as life permits it).
During my initial testing of starting my all-in-one VMWare ESXi environment (which contains a Virtual SAN and VM’s on 1 host), I noticed that the autostarting of VM’s was not working properly. (This is with ESXi v5.0 so I don’t know if this is also affecting v5.1 and beyond)