SQL2012 System Databases Restore on a different environment

Question

So While I was playing around I wondered if it was possible for me to setup a similar version of SQL 2012 on a different environment and restore it quickly.  
Master Env
SQL 2012  - 3 databases , 2 SSIS packages , 2 Sql Agent jobs and 1 report.
The idea would be to copy this on another Server altogether.
Slave Env
So the first thing I thought was the system database should go across before all else.  Now it states that both versions have to be the same which I confirmed using;
Use Master
Go
SELECT
SERVERPROPERTY
('ProductVersion
')ASProductVersion,
SERVERPROPERTY
('ProductLevel')ASProductLevel,
SERVERPROPERTY
('ResourceVersion')ASResourceVersion,
SERVERPROPERTY
('ResourceLastUpdateDateTime')ASResourceLastUpdateDateTime,
SERVERPROPERTY
('Collation')ASCollation;
Both showing the same.    Having backed up both system databases on both sides the restoring of the model and msdb databases where straight forward.
The master was a different ball game and is one I still cant get past
1. Stopped the SQL SERVER on the Slave Env
2. Open Command shell
3. Net Start MSSQLServer /m”SQLCMD”
4. sqlcmd -S. -E
5. RESTORE DATABASE master FROM DISK = 'D:\SQL\Backups\master.bak' WITH REPLACE
Go
what this will do is restore the master database from the live to the slave and this is where the problems begin because once you do that restart the SQL server and get out of single user mode you cant logon .
Question
Assuming the Master has different windows logons to the Slave is there any way once this restore has been done to negate this or do you  create a user straight after the restore?
Also with ReportingServices and Integrated Services are they straight forward Db restores ?
Any Help one this would be great!!
As I really want to know how quickly I can jump from one environment to another.

Answer 1

So While I was playing around I wondered if it was possible for me to setup a similar version of SQL 2012 on a different environment and restore it quickly.  
Master Env
SQL 2012  - 3 databases , 2 SSIS packages , 2 Sql Agent jobs and 1 report.
The idea would be to copy this on another Server altogether.
Not very simple. Requires DBA skills.
The standby (secondary) server usually refreshed through database mirroring or log shipping.
BOL: " About Log Shipping (SQL Server)
SQL Server Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. The transaction log backups are
applied to each of the secondary databases individually. An optional third server instance, known as the monitor server, records the history and status of backup and restore operations and, optionally, raises alerts if these operations fail to occur as scheduled.
Benefits
•Provides a disaster-recovery solution for a single primary database and one or more secondary databases, each on a separate instance of SQL Server.
•Supports limited read-only access to secondary databases (during the interval between restore jobs).
•Allows a user-specified delay between when the primary server backs up the log of the primary database and when the secondary servers must restore (apply) the log backup. A longer delay can be useful, for example, if data is accidentally changed on the
primary database. If the accidental change is noticed quickly, a delay can let you retrieve still unchanged data from a secondary database before the change is reflected there. "
LINK: http://msdn.microsoft.com/en-us/library/ms187103.aspx
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012