I have a virtual machine with Windows server 2012 on google server (like amazon EC2).
How can I configure the Google machine for work:
Monday to Friday 08:00 am to 18:00 pm machine on...
Saturday and Sunday machine off
Related
How to use Windows Server 2012 and 2008 as an AWS instanace in free tier account? I am having free tier account on AWS, so can I use Windows Server as my instance?
From AWS Free Usage Tier:
AWS Free Tier (Per Month):
Elastic Compute Cloud (EC2)
750 hours of Amazon EC2 Linux t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
750 hours of Amazon EC2 Microsoft Windows Server t2.micro instance usage (1 GiB of memory and 32-bit and 64-bit platform support) – enough hours to run continuously each month
Note that the restriction is on the instance type -- it needs to be a t2.micro instance (but possibly also includes the older t1.micro).
When launching an Amazon EC2 instance, select an Amazon Machine Image (AMI) that says "Free tier eligible". This currently includes:
Microsoft Windows Server 2012 Base
Microsoft Windows Server 2008 R2 Base
Microsoft Windows Server 2003 R2 Base
I have a Windows 2012 Server and client PS's get clock data from the server but server clock delays like 5 mins in 6 months. How can I fix that?
we have some cloud Services hosted in Windows Azure and also some Azure SQL database. At night (during 4:00 - 6:00 utc) there are running some Jobs to import data into database. Since some weeks all the Jobs fails with an timeout expired exception of the database. If I run the Jobs later (during 7:00 - 9:00 utc) on my local machine within the Emulator, all Jobs work without any Problems on the same database.
At the mport time is no much traffic from our site on the database server. The monitoring of the manage portal shows that there are not many open Connections, no throttled ones and no connection errors. There are much more traffic during my local runs.
The sys.event_log do not contains any errors or other possible issues.
Are there any logs or other Options to get more Information about why the Jobs failed at night?
Update
It seems, that the SQL Azure Server ignores the command timeout property. The Jobs start at 4:30 UTC and stops with an timeout exception at 4:37. But the query, which gets an timeout, has an command timeout of 1200 (20 minutes). And before starting the command, there are some downloads from an ftp-server, file parsing and other SQL queries.
Just to note that SQL Azure isn't a full version of MS SQL and does have some limitations. Most notable limitation is the infrastructure that its built on. Your SQL Azure DB will be hosted on a Small Instance server that has shared resource with hundreds of other users. Although there is a fair use policy on the machines it does take time for the servers to kick in.
My suggestion would be to have some way of determining if the Job is actually starting or if the connection pool is timing out prior to starting the job. I.E. create a jobs table that is inserted into to say its started and have this as the first action on your job.
Alternatively you could think about migrating to a VM setup in Azure. This is where you have a Small or Medium instance VM with a fully fledged version of MS SQL Server running on it. That way you can run your jobs against the server correctly and control you connection pooling more appropriately.
I have a single Windows 2012 Server and trying to configure it for 2 independent purposes:
(1) DB Server MSSQL-2012
(2) VDI for about 5 clients.
I understand more or less how everything works but I'm little uncertain how the VM's should be nested into a single server. Should the Base Server manage the VDI Pools OR should a separate VM be created to manage VDI??
Base Install -- Windows 2012 Server with Hyper-V Role Enabled
(VM) - Windows 2012 Server with MSSQL
(VM) - Windows 2012 Server to Manage VDI Pool
(VM) Client VDI
(VM) Client VDI
(VM) Client VDI
The best thing to do is review Microsoft's LAB setups for various (and clearly defined) VDI scenarios. VDI QuickStart
On Amazon (AWS) EC2 Windows Server 2008
This line of C# code
File.Copy(file1, file2);
is executed first time about a minute, when repeated - in no time
Any ideas?