Next part of client installs – iOS
Search for and install the client from the App store
Press ‘Add Server’ and type in the server name
Tap the Cloud icon for the your server and if necessary, choose your appropriate desktop pool and then enter your given username and password. Domain should auto populate, but is add if required.
You can make changes to various settings, such as the resolution (if required) from the settings menu.
Enter username and password
You’ll either go straight in, or have options if you are entitled to more than one pool. Choose what you’re due and you’re in.
For most of us, it’s easy installing any kind of client app, or app on our phones. For others, it can be a little bit more challenging. I snipped (Love the snipping tool and PSR, but that’s another story) and borrowed some screenshots to build up a few documents for the client installs for View – as I couldn’t find anything official and I needed them for a project. Without further ado, here’s android – iOS and Windows follows later.
Search for and install the client from the App store
Add the View Connection Server address you need
Enter your given username and password
Choose the appropriate Desktop pool if given the option
I hate certificates. Well, a nice wildcard cert deployed internally is fine, but when there’s a faff to replace certificates and it’s been so long, that you really cannot remember what you did in the first place…I just hate it. So imagine my childish delight when I had to build AD CS!
It’s not that bad in all fairness and it boils down to make server, add role, next next next and let AD do it’s magic for all machines you need sending the certificate to within the domain. That’s just reminded me about the VDM certificate for connection servers, which will come later on.
I followed the MS lab guides and also backed this up with a very nice blog post with pretty screenshots and all worked fine. Just remember to add in any subject alternative names if you have a mixture of FQDN and abbreviated server names within your domain.
AD CS and PKI
Deploying Standalone Root CA (Server 2012)
Ok, so you may have set up AD, done your Domain and it all works and the world is a happy place. But Alas! You now have to deal with the Branch Office. Dead easy. You got your connection to it? Check. You know the name you want to use? Check. You got the subnet? Check.
Read these and be done with it!
Step by Step Set up
There considerations such as the Cost (really for multiple sites) and the Replication schedule. I’ve always found the traffic/bandwidth use, to be minimal, but your mileage may vary depending on those underground wires you’re connected to. Or satellite. Or point to point laser link (Pew pew! Aw it’s foggy it doesn’t work anymore!)
Over the years I’ve amassed a huge amount of AD related information. Most of it at the moment I’m working through is about creating a Forest/Domains, OU structure, logical/Geographical models and I think if you need to do that… You probably know how to or where to get the information to do it! All the MS stuff is easily accessible so it’s a bit pointless me posting everything I’ve ever read on it.
One thing that is of use and that bypasses the need to actually…Pay for things is a very old school way of making pretty pictures from AD. It doesn’t work on server 2012, so it will need playing with, but it saves a ton of time working through text documents, AD users and computers, then Visio:
AD Visio Tool
New server built. Need access to vSphere or any other web based, server or appliance web front.
Are you sure?
Do you trust this site?
Do you really trust this site?
Are you sure you trust this site?
Are you really sure you really trust this site?
Just turn it off via GPO
Disable IE Enhanced mode
In all fairness, some people have security concerns about using any browser on a server. I get that. If you’re using server 2012 R2, relatively recently updated and well… You aren’t an idiot, you’re probably OK using it to get media from a trusted site, or use your web based admin pages. Final decision lies with you!
There are situations and environments, where you may have apprentices, or non IT literate staff who are the IT staff; I’ve been involved with a lot of places where they don’t have anyone in an official IT capacity and the highest qualified person is the one who can change the lockscreen on their phone – where you shouldn’t do this and in fact, should lock it all down as much as you can.
Ah, good old DFSR, with it’s highly complex management algorithm that is at times, a Law Unto Itself. What do you mean that file is newer? I’m going to overwrite it with THIS one!
DFSR is also full of false truths and true lies. Event ID’s that don’t tell you what’s wrong. Logs that make out that everything is broken when it isn’t… Weeks of over written data that no one knew was happening… But sadly if you don’t have hardware replication, you probably use this. Don’t get me wrong, when it works properly, it’s great, but there’s sometimes quite a management overhead, plus a lot of time and experience involved when it needs to get fixed.
This link has an amazing script that was similar to part of my checks in a previous role, whereby I had a few scripts running as part of Daily Checks for the team, that reported on DFSR, Exchange and AD. It emailed pretty pictures and everything (you know how people love pretty pictures!) So as my first post towards Checks and DFSR management – the following link is fantastic.
DFSR Monitoring Script
I will say though, as part of any infrastructure related checks or notifications, it’s what works for you and your team. I had a great Project Manager once who said that if you get the process right, then everything works. If the process fails and a person followed the process, then the process needs changing. Which stands to reason – you need the process that people need to follow, that takes into consideration everything that needs to happen and there’s no point having a barrage of alerts sent to email, if the person involved doesn’t read them, understand them and put down somewhere he’s done all of the above.