Going to need a LOT of help in future

[SimpleSi]

I've just taken over a school that has one of these newfangled domain windows server setups that I've sucessfully avoided for 15 years

 

So be gentle with me as I ask the REALLY basic questions.

 

Worse still - its server2012 with Win8 type interface

 

Simon

[3s-gtech]

You'll need to spend time getting used to the Active Policy gubbins and this new fangled 'Group Policing'. Server 2012 R2 must only be used via a touch interface, and the Start screen is really easy to configure and work with.

 

 

 

 

/have fun!

[tomo1095]

What? You've avoided windows server environments for the past 15 years? How? - Any advice?

 

But joking aside, get your head around Active Directory and Group Policy and you'll be fine! I believe in you.

[jmak]

Server 2012 R2 must only be used via a touch interface,

 

 

 

 

/have fun!

 

Is my sarcasm sensor failing or are you a masochist?

I've just taken over a school that has one of these newfangled domain windows server setups that I've sucessfully avoided for 15 years

 

So be gentle with me as I ask the REALLY basic questions.

 

Worse still - its server2012 with Win8 type interface

 

Simon

You will need to get your head around Group Policy and Active Directory, but I've found the principles to be very logical. At the risk of introducing an extra complication, I'd suggest getting RSAT (remote server administration tools) installed on your workstation. You then configure everything from your machine and for the most part don't have to find your way round a new operating system - it's just another applposition

 

Edit: And of course you've already worked out the solution to most things - ask on here and someone will help [emoji3] . I've answered this one, because I have the relevant experience of being in your position!

Edited May 5, 2016 by jmak

[3s-gtech]

Your sarcasm sensor needs a reboot. I suggest maybe running it on a nice stable OS like Vista RC.

[SimpleSi]

1st question - I want to deploy an updated package

previous was crumblexxxx.msi - now I want to update all computers to crumbleyyyy.msi

 

I've found a shared folder with old msi in it so I've put new one their as well

 

Now I've found a gpo called Deploy Crumble with the old msi in it

've

 

Do I

1. Ignore this and create a new object and deploy that

2. Just add in new msi

3. delete old msi entry

 

something else

 

PS I've just sucessfully removed C drive restriction on curric computers so I've got some grasp of how to do stuff but its the little details that elude me

[3s-gtech]

My personal experience is that managing MSIs with install scripts is a little easier, especially for software that frequently updates. I guess this is because newer versions haven't always installed nicely on top of the old.

 

To manage that, I use a startup script:

 

msiexec /x \\server\share\crumblexxxx.msi

msiexec /i \\server\share\crumbleyyyy.msi

 

First line removes the old version (if it's present, otherwise it skips), the second installs the new. Then you can just add to the script as new versions come out, changing the last version to /x.

 

msiexec /x \\server\share\crumblexxxx.msi

msiexec /x \\server\share\crumbleyyyy.msi

msiexec /i \\server\share\crumblezzzz.msi

[FN-GM]

What? You've avoided windows server environments for the past 15 years? How? - Any advice?

 

Using Windows 98 as a server

[SimpleSi]

So the 1st answer to my question on how to use GPO to deploy msi's is don't!!!!!!

 

#lol

[DJ-1701]

1st question - I want to deploy an updated package

previous was crumblexxxx.msi - now I want to update all computers to crumbleyyyy.msi

 

I've found a shared folder with old msi in it so I've put new one their as well

 

Now I've found a gpo called Deploy Crumble with the old msi in it

've

 

Do I

1. Ignore this and create a new object and deploy that

2. Just add in new msi

3. delete old msi entry

 

If you want to update all the machines that had the previous version in one go, what you would do is delete the old MSI from the GPO setting, selecting the option 'Immediately uninstall the software from users and computers'. You would then add the new MSI in.

 

On next reboot the machines should remove the old version, then install the new version. After this completes the users will then eventually be able to login and use the machine.

[Matt_Renato]

 

Worse still - its server2012 with Win8 type interface

 

Simon

 

If that server is only running 2012 I'd look at upgrading it to 2012 R2 over the summer. It's a pretty painless process.

[3s-gtech]

Unless it's running Exchange

[Matt_Renato]

Good point!

[PR-UK]

I used to deploy MSI's via GPO before we had things like SCCM and didn't have any issues.

 

If the old version deployed ok just add the new version to the same GPO leaving the old one present, when you add the new one you can specify it's an upgrade to the old package and it will upgrade the machines at startup (once the policy has applied).

 

Obviously test this!

[psydii]

Here is the bible. Its 17 years old now, and some of the details around replication and backup have changed a little but it covers the fundamentals.

https://msdn.microsoft.com/en-us/library/bb727030.aspx

https://technet.microsoft.com/library/Cc977985

 

 

Similarly here is the best resource for Group Policy form the same era.

https://technet.microsoft.com/library/Cc978213

(note: it does not cover the GPMC and the Remote OS installation changed completely in 2003 and then again in the vista era)

Updated information here: https://technet.microsoft.com/en-us/library/cc778005(v=ws.10).aspx

and here: https://www.microsoft.com/en-us/download/details.aspx?id=24449

 

 

The principles of User State Virtualisation or IntelliMirror as it was branded then (Offline Files + Folder Redirection + Roaming Profiles) remain true, though the details are substantially different since Vista. A more modern take can be sound here: https://msdn.microsoft.com/en-us/library/ff877478.aspx

 

 

If you can get hold of it the Windows 7 Resource kit covers a lot of ground on these topics too.

[Arthur]

Using Windows 98 as a server

It must have been Windows ME. That was released 15 years ago.

[jmak]

So the 1st answer to my question on how to use GPO to deploy msi's is don't!!!!!!

 

#lol

You'll get a range of answers - personally I can't script (I can follow someone else's and make basic customisations) so I prefer to stick to deploying by group policy. Everything will probably go horribly wrong because I'm writing this down, but I find GP deployment pretty reliable and got my head round it pretty quickly.

[SimpleSi]

Immediately uninstall the software from users and computers

 

where do I find that menu item please?

[3s-gtech]

Not a menu item - it shows when you remove an assigned package (msi) from the Software Installation section.

[SimpleSi]

Oops - I'd already removed it! Never mind - live and learn

 

I've found an option that says Group Policy Update and it then offered to update 27 computers - yippe I thought - pressed it and got 27 errors

 

26 of them say the remote procedure call was cancelled

1 said RPC server is not available

 

The logon scripts idea is looking better and better option but I feel I should try and do this "properly"

[SimpleSi]

Is it possible that this domain hasn't been fully configured to allow installing msi's via GPO?

 

The GPO restrictions are working !!!! (Unfortunately) - I'm hoping to find where windows key-R is disbabled before half-term

[3s-gtech]

Go steady. User Configuration\Policies\Administrative Templates\Start Menu and Taskbar\Remove Run menu from Start Menu

 

If you allow this, there can be potential for some shenanigans, but it's fairly safe if you have everything else locked down. It can be very annoying if it doesn't work for admins though!

 

No extra configuration needed to make MSIs work. They need to be within a UNC share with correct permissions, and then they 'just work'!

[SHimmer45]

make sure authenticated computers have read access to the share where the MSI are being pointed two in your policy

[SimpleSi]

I've got run on the menu but it give the restriction msg if I click on it!

 

Progress (of some sort on MSI deploy) 1 laptop (and 1 only) has installed my MSI - none of the others yet though!

[SimpleSi]

make sure authenticated computers have read access to the share where the MSI are being pointed two in your policy

 

??? When I look at share and security permissions on the MSI folder - I don't have an authenticated computer option to add - the only thing starting authenticated is authenticated users

 

I presume I'm looking in wrong place?