PopCap's (almost) entire PC and Mac catalog is 50% off originally appeared on Joystiq on Wed, 29 Dec 2010 00:30:00 EST. Please see our terms for use of feeds.
Wednesday, December 29, 2010
PopCap's (almost) entire PC and Mac catalog is 50% off
Blog Post: Azure@home Part 13: Remote Desktop Configuration
This post is part of a series diving into the implementation of the @home With Windows Azure project, which formed the basis of a webcast series by Developer Evangelists Brian Hitney and Jim O?Neil. Be sure to read the introductory post for the context of this and subsequent articles in the series.
As you likely know by now, the web and worker roles deployed as part of Azure@home, or as part of any Azure application for that matter, are ultimately hosted in a virtual machine (VM) running somewhere in the Azure data center that you selected for your application. Until recently though, that was about all you knew. The VMs are managed by the Azure fabric running through the data center - from the point you deploy your code, through upgrades, hardware failures, and operating system updates. Sometimes though it would be great to take a look at your running application for monitoring, troubleshooting, or simply curiosity!
In this post, I?ll cover how to set up the deployment of an Azure application, specifically Azure@home, for remote desktop access, and in a follow-up post, I?ll take some time to poke around at live instances of the WebRole and WorkerRole within Azure@home.
Configuring the Application for Remote Desktop
Visual Studio Tooling Support
The easiest way to set up an application for Remote Desktop access is when you publish the Azure cloud service project from Visual Studio. A link on the Deploy Windows Azure project dialog brings up a second dialog through which you can enable and configure Remote Desktop access.
Remote Desktop configuration requires installing a certificate in Windows Azure that will be associated with the hosted service (namely your deployed Azure application). You can browse the certificates (in your Personal certificate store) via the dropdown list on the Remote Desktop Configuration dialog and select one, or just create a new one.
Certificates for Remote Desktop access require a KeySpec of AT_EXCHANGE versus AT_SIGNATURE. If you are using the makecert utility, specify the
?sky switch with a value of exchange (or 1). Exchange keys can be used for signing and encrypted session key exchange, whereas signature keys are only for authentication (digital signing). certutil is a great resource for peering into your certificate configurations and seems to provide more information than the Certificate Manager tool (certmgr.exe) or MMC plug-in (certmgr.msc).If you elect to create a new certificate (via the last option in the certificate drop down list), you?ll be prompted for a friendly name. Next, you specify a user name, password, and expiration date; these are used to set up a temporary account on the remote VM which you will be accessing.
The net effect of these modifications is to add configuration settings in both the ServiceDefinition.csdef and ServiceConfiguration.cscfg files associated with the Windows Azure cloud services project. You can also make these modifications (detailed next) in the XML editor directly.
ServiceDefinition Modifications
In the definition file, module import directives are associated with each of the roles in the Azure application. For Azure@home, the updated file looks like the following, with the highlighted lines indicating the additions.
<?xml version="1.0" encoding="utf-8"?><ServiceDefinition name="AzureAtHome" upgradeDomainCount="2" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition"><WebRole name="WebRole"><Sites><Site name="Web"><Bindings><Binding name="HttpIn" endpointName="HttpIn" /></Bindings></Site></Sites><ConfigurationSettings><Setting name="DiagnosticsConnectionString" /><Setting name="DataConnectionString" /></ConfigurationSettings><Endpoints><InputEndpoint name="HttpIn" protocol="http" port="80" /></Endpoints><Imports><Import moduleName="RemoteAccess" /></Imports></WebRole><WorkerRole name="WorkerRole"><ConfigurationSettings><Setting name="DiagnosticsConnectionString" /><Setting name="DataConnectionString" /><Setting name="FoldingAtHome_EXE" /><Setting name="AzureAtHome_PollingInterval" /><Setting name="AzureAtHome_PingServer" /></ConfigurationSettings><LocalResources><LocalStorage name="FoldingClientStorage" cleanOnRoleRecycle="false" sizeInMB="1024" /></LocalResources><Imports><Import moduleName="RemoteAccess" /><Import moduleName="RemoteForwarder" /></Imports></WorkerRole></ServiceDefinition>
Each role in the project imports a RemoteAccess module, which means every VM hosting an instance of those roles will be eligible for remote access.
Also, exactly one role in the project (here, the WorkerRole) imports the RemoteForwarder module. The role marked as RemoteForwarder receives all of the Remote Desktop traffic that flows to the application and then routes it to the appropriate role instance. You can mark an existing role as the RemoteForwarder or use a dedicated role (perhaps deployed on an extra-small instance) to better isolate the Remote Desktop traffic from your own application role instances.
ServiceConfiguration modifications
The ServiceConfiguration.cscfg file is likewise modified to contain specific values relating to the remote desktop access. Below you can see new ConfigurationSettings corresponding to the remote account user name, password, and expiry. Also included is a separate Certificates section to indicate the certificate used to exchange the account information via the Remote Desktop session. Configuration for the WebRole is identical with the exception that there is no markup to enable the RemoteForwarder, since only one role in the Azure project needs to incorporate and enable this module.
<Role name="WorkerRole"><Instances count="5" /><ConfigurationSettings><Setting name="DiagnosticsConnectionString" value="DefaultEndpointsProtocol=https;AccountName=azureathome;AccountKey=REDACTED" /><Setting name="DataConnectionString" value="DefaultEndpointsProtocol=https;AccountName=azureathome;AccountKey=REDACTED" /><Setting name="FoldingAtHome_EXE" value="Folding@home-Win32-x86.exe" /><Setting name="AzureAtHome_PollingInterval" value="15" /><Setting name="AzureAtHome_PingServer" value="http://distributed.cloudapp.net" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername"
value="jimoneil" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword"
value="REDACTED" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration"
value="2011-01-27T23:59:59.0000000-05:00" /><Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" /></ConfigurationSettings><Certificates><Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption"
thumbprint="REDACTED"
thumbprintAlgorithm="sha1" /></Certificates></Role>
If you only wish to expose one role for remote access, you can do so, but you have to modify the configuration file XML yourself. In fact, if you change any of the Remote Desktop configuration values generated by Visual Studio (even flipping a value from true to false), when you subsequently click the Configure Remote Desktop connections? link in the Visual Studio publish dialog, you?ll get a message box indicating that the Remote Desktop configuration was not generated by Windows Azure Tools, and you must use the Xml editor to modify the configuration.
Create Service Package
As the final step in Visual Studio, I?m opting to create the service package directly, via the Publish option. As you might recall, this creates two files on the client machine, a .cspkg file and a copy of the .cscfg file, that you can then upload via the Windows Azure Management Portal into a new hosted service.
Alternatively, you can set up credentials on the client to deploy directly to Azure; however, to do so you must first set up a hosted service in the Azure portal and also install a management certificate to associate with your Windows Azure subscription.
In either case, the Remote Desktop Configuration aspect of the deployment remains the same as what we configured earlier in this article.
Configuring the Azure Service Deployment for Remote Desktop
In the Windows Azure Management portal (I?m using the new portal launched after PDC 10), you can deploy the package and configuration files and install the certificate required for remote desktop access in the same step.
Exporting the Remote Desktop Certificate
First though, you?ll need to export the certificate created above into a PKCS#12 formatted file stored on your local machine. You can do that easily via the Certificate Export Wizard launched from the certmgr.msc MMC plugin, as shown in the short video clip below (note: there is no audio).
Deploying the Azure Service (and Certificate)
Now that you have the certificate file, service configuration document, and service package file on your development machine, you?re ready to deploy the service to Azure via the Windows Azure Management Portal. You can browse to the two service files directly from the Create a new Hosted Service dialog (below) and of course, select the target data center region, service URL, and deployment type (staging or production).
The Add Certificate button spawns a separate dialog (stylized below) via which you browse for the certificate file exported earlier and also supply the password that secures private key in the .pfx file (this is the same password you specified when exporting the certificate via the wizard in the previous step).
Once the service has been deployed, you?ll see something along the lines of the following in the Windows Azure Management Portal. Note that each of the individual role instances is represented; there are two instances of the Azure@home web role and five instances of the worker role in this deployment. Also included below the highlighted service is the certificate we uploaded with the cloud application.
Accessing an Instance via Remote Desktop
The Windows Azure Management Portal allows you to modify the Remote Desktop configuration as well as launch a Remote Desktop session.
Modifying Remote Desktop Configuration
When you select a Role node (not an instance node) in a deployment configured for Remote Desktop, the Enable checkbox and Configure option in the upper right of the Windows Azure Management Portal ribbon menu are enabled. Choosing Configure brings up the dialog below to set the credentials for the Remote Desktop session as well as modify the certificate and expiration date (values we initially supplied in the Remote Desktop Configuration dialog in Visual Studio)
Connecting via Remote Desktop
To connect via Remote Desktop to a specific instance running in the Azure data center, select a node instance, and then press the Connect button in the upper right of the portal?s ribbon menu, as shown below:
You?ll be prompted to access a file with a .rdp extension that?s downloaded on your behalf; press Open, then Allow, and finally Connect if and when prompted; you can elect not to be prompted again on subsequent connection attempts.
Tip: save the .RDP file locally and you can bypass the Windows Azure Management Portal whenever you want to Remote Desktop in to the VM instance again.
When you press Connect on this final dialog (which is noting, as we?d expect, that the self-signed certificate provided cannot be verified), the Remote Desktop session starts up, prompting you for your credentials (see right), namely the user name and password you specified in the Visual Studio Remote Desktop Configuration dialog at the outset (or that you perhaps modified via the Windows Azure Management Portal).
Once you have supplied valid credentials, you should be logged in to the VM instance hosting the selected role, like below! If it?s the first time you?ve accessed this VM, you?ll see that your user account is first configured ? as it would be for any new user on a Windows system. Once that?s done (and presuming the VM has not restarted), on subsequent logins you?ll be able to resume whatever you were doing in your last session.
At this point the VM is yours to explore, and that?s where we?ll pick up things on the next post in this series.
LOGITECH INTERNATIONAL MCAFEE MAXIMUS MANTECH INTERNATIONAL MANHATTAN ASSOCIATES
Tuesday, December 28, 2010
Why is Bioanalytical Systems So low? Money Flow Is Key
Michael Bryant submits:
Complete Story »
To take a quote from Bloomberg, “Follow the money.” Analysing the flow of money can help when determining when to buy. But it is important to do fundamental analyisis on the stock to confirm if it is a good buy. Here is the analysis on one stock, Bioanalytical Systems (BASI), a service and equipment provider to the pharmaceutical, medical, and biotechnology sector. New drugs are always being developed, and the company provides the services and equipment to make this happen.
Money flow (MF) = number of shares traded X change in closing price
Complete Story »
SYKES ENTERPRISES INORATED SYBASE SUN MICROSYSTEMS STANDARD MICROSYSTEMS SRA INTERNATIONAL
The Best Of Big Download: December 20-26
Exclusive Features
- Big Download's 2010 Best PC Game Awards - We pick our favorite games of the past 12 months. Plus we have our picks for the 2010 PC Game Vaporware Awards and our picks for the top 10 biggest PC game news stories of the year.
- The Next Decade of PC Gaming - What technologies will be a part of PC games in the next 10 years? We offer our predictions.
- The Most Anticipated PC Games of 2011 - We begin our multi-part look ahead to 2011 with our picks for our most anticipated first person shooters.
- Interviews - We chat with the folks behind games like Back to the Future, Bastion, The Oddbox, Bloodline Champions, and Blight of the Immortals. We also have the first ever interview with the new president of the PC Gaming Alliance.
- Divinity 2: The Dragon Knight Saga Review - We give our final verdict to this revamped version of the fantasy RPG.
Continue reading The Best Of Big Download: December 20-26
The Best Of Big Download: December 20-26 originally appeared on Joystiq on Sun, 26 Dec 2010 23:30:00 EST. Please see our terms for use of feeds.
Monday Reads
Here are the latest additions to my Instapaper: ? Heads Up Play With David Einhorn (Dealbreaker) ? What we have here is one of the great comeback stories in the history of competitive punctuation: The Hash Mark (National Post) ? Transcript: The Assange interview (BBC) ? So you want to be a viral video? (Fortune) [...]
D: Dive Into Mobile: The Full Interview Video of Google Ad Head Susan Wojcicki
Will Google dominate mobile advertising in the same way that it's ruled the online search ad business?
Susan Wojcicki, who was key to that first huge success, is in charge of making sure lightning strikes twice for the Silicon Valley search giant.
Susan Wojcicki, who was key to that first huge success, is in charge of making sure lightning strikes twice for the Silicon Valley search giant.
Hydro Thunder Hurricane discounted on Xbox Live for the day
Of course, you may be in the Marketplace for something different. Like a pet "mini-taur" for your Avatar? On sale for 120 points, you could make a case for it being the best deal of the day. (But you'd be wrong.)
Hydro Thunder Hurricane discounted on Xbox Live for the day originally appeared on Joystiq on Mon, 27 Dec 2010 10:00:00 EST. Please see our terms for use of feeds.
Stranger's Wrath HD dev will 'look to' bring PS3 update to PC for free
Porting the title from Xbox (and an Xbox-specific implementation of DirectX) to PC and OpenGL introduced a number of issues, which Gilray was eager to address. "From a personal note, to read these comments that the game is beyond broken hurts," he wrote in the forums. "I am always incredibly paranoid about that work I/we do and am always self-critical, so please help us fix these issues by providing as much positive feedback as you can with system specs and detailed descriptions."
As users turned in (generally angry) bug reports, one asked the question everyone's been wondering: "Why can't the PC port be as good as the PS3 version?" Gilray responded simply, "Because the PS3 version is not completed yet," before adding, "As for the PS3 version, we will look to bring this to the PC as an update to the current PC version at a later date." While it's far from a promise, it is a reminder that the HD remake isn't contractually bound to remain a PS3-exclusive, and it's also a potential silver lining for anyone plagued by bugs in the current Oddboxx release. [Thanks, BoogerA]
Stranger's Wrath HD dev will 'look to' bring PS3 update to PC for free originally appeared on Joystiq on Tue, 28 Dec 2010 12:31:00 EST. Please see our terms for use of feeds.
ROCKWELL AUTOMATION RF MICRO DEVICES RED HAT RADISYS RACKABLE SYSTEMS
Apple Has eBay Kill Off Auctions Of Steve Jobs Figure It Doesn't Like
Remember, a few weeks back, how Apple went after a Chinese company making Steve Jobs figurines and forced it to stop selling them? As you might expect, the attention from the legal threat only served to create much more interest in the figurines, and the few folks who got their hands on them before the offering was shut down, quickly moved to eBay, where they started selling for thousands of dollars... until Apple complained and eBay killed all of the auctions under its VeRO program. This actually strikes me as a bit odd. I could see Steve Jobs making the request, but should eBay listen to a company that requests a takedown of an individual's likeness, even if that individual is the company's CEO? After all, Apple does not own Steve Jobs' likeness... 
Of course, we still think it's silly that Apple's so worked up about all this in the first place.
Permalink | Comments | Email This Story
Permalink | Comments | Email This Story
IKON OFFICE SOLUTIONS IDT IBASIS HYPERCOM HEWLETT PACKARD CO
Gibson Gets An Injunction Over PaperJamz; Retailers Ordered To Stop Selling Them
If you happened to have received a PaperJamz guitar toy for the holidays this year, you may want to hang onto it as a collectors' item. In November, we wrote about how Gibson, the famed guitar company, was suing a bunch of companies over PaperJamz. The main target, of course, was Wowwee, the toymaker who makes the devices (which are plastic -- not actually paper -- guitars with a capacitive touch screen that turn your air guitaring into something a bit more real), but Gibson also sued a bunch of retailers, including Walmart, Amazon, eBay, Target, etc. for selling the toys.
Eric Goldman now lets us know that Gibson successfully got an injunction against all the defendants, with the court ordering them to stop selling the toys, just days before Christmas, though the defendants quickly appealed the ruling. The full injunction is embedded below.
When we first posted this story, there was an interesting discussion in the comments. Many people felt that Gibson was definitely in the right here -- as the designs did seem pretty clearly to copy Gibson designs. I still question how much (if any) "harm" this actually does to Gibson, and wondered why Gibson wouldn't just use this as an opportunity to market its own products more -- and maybe even offer upsell opportunities for PaperJamz users.
However, what may have been more interesting were claims in the comments that Gibson's lawyers misidentified a bunch of websites in the initial lawsuit. The lawsuit claimed that Wowwee's own websites acknowledged that the styling was modeled after Gibson's guitars, but apparently, at least some of those websites may not have actually been Wowwee's at all, but third parties, who were simply pushing people to Amazon affiliates or other sites. If that's the case, it calls into question certain aspects of the rest of Gibson's case as well.
Permalink | Comments | Email This Story
Eric Goldman now lets us know that Gibson successfully got an injunction against all the defendants, with the court ordering them to stop selling the toys, just days before Christmas, though the defendants quickly appealed the ruling. The full injunction is embedded below.
When we first posted this story, there was an interesting discussion in the comments. Many people felt that Gibson was definitely in the right here -- as the designs did seem pretty clearly to copy Gibson designs. I still question how much (if any) "harm" this actually does to Gibson, and wondered why Gibson wouldn't just use this as an opportunity to market its own products more -- and maybe even offer upsell opportunities for PaperJamz users.
However, what may have been more interesting were claims in the comments that Gibson's lawyers misidentified a bunch of websites in the initial lawsuit. The lawsuit claimed that Wowwee's own websites acknowledged that the styling was modeled after Gibson's guitars, but apparently, at least some of those websites may not have actually been Wowwee's at all, but third parties, who were simply pushing people to Amazon affiliates or other sites. If that's the case, it calls into question certain aspects of the rest of Gibson's case as well.
Permalink | Comments | Email This Story
LM ERICSSON LOGITECH INTERNATIONAL MCAFEE MAXIMUS MANTECH INTERNATIONAL
Net Neutrality Win Could Be Hollow Victory
Net neutrality framework seems to cave on key issues that will render it ineffective for protecting the open Internet.
DIGITAL CHINA HOLDINGS DIRECTV GROUP ELPIDA MEMORY EMC FIDELITY NATIONAL INFORMATION SVCS
Subscribe to:
Comments (Atom)