Swarm's New Update Works Great Without Friends. Foursquare’s Swarm 5. OS and coming soon to Android, has a cleaner look and better venue categorization. Most importantly, it downplays most of the social check- in app’s social elements and strengthens its solo benefits. That’s great news, because Swarm might be more useful if you use it alone. The early promise of Foursquare (and its predecessor Dodgeball) was to help people meet up with their friends by selectively sharing their location.

This would give people a sort of social radar that let them meet up ad hoc. Unlike Google Maps or Apple’s Find Friends, Swarm leaves the user in control of each check- in, making it less exhibitionist but also less frictionless.

Yesterday Foursquare updated to allow your friends to check you in to places (with your. But not even Facebook could convince people to report every time they showed up at a bar or restaurant. Instagram, Twitter, and Snapchat adopted location tags too, but while this makes for excellent after- the- fact content aggregation, most people don’t use it frequently enough to enable serendipity- based drop- ins. Swarm’s social elements (like becoming “mayor” of your favorite venue or collecting points for weekly contests) aren’t that useful unless your friends are fellow diehards. As a longtime diehard (and acquaintance of Foursquare’s founders) I’ve seen fewer and fewer of the early core users check in, while newer friends have never joined.

The social panel of the app has become a ghost town populated by people I knew better in 2. But that hasn’t discouraged me from checking in (which now often takes just a swipe and a tap from your lock screen). I’m not here for the points or even the casual hangouts; I’m here to keep a journal of where I’ve been, which I end up consulting several times a week. Foursquare is fairly open about Swarm 5’s shift toward solo features. This was the focus for Swarm 5. The company still benefits as long as you’re providing it data, which it then sells to advertisers. According to Wired, “ad- targeting and other services allow the company to make money from a relatively small user base.” As usual, the service is free because you’re the product.

Foursquare’s Swarm 5.0, released yesterday on iOS and coming soon to Android, has a cleaner look and better venue categorization. Most importantly, it downplays. STIG Description; The Windows Server 2012 / 2012 R2 Member Server Security Technical Implementation Guide (STIG) is published as a tool to improve the security of. Latest trending topics being covered on ZDNet including Reviews, Tech Industry, Security, Hardware, Apple, and Windows. Games Sonic Final Fantasy X7 Hacked Games.

Or in another sense, you’re the free labor, and the database you’re building is the product. Not a bad trade- off.

Swarm’s main display used to show where your friends had checked in. Now that display shares equal billing with a solo view, displaying a timeline and map of your past check- ins. You can share this map, but more importantly, you can analyze it next time you’re trying to remember what you did Friday night, or returning to your old neighborhood and wondering what to eat. Your Swarm check- ins also help Foursquare customize your recommendations, which gives it an edge over Yelp, but you can already customize your recs by answering some questions about your tastes. Check- ins also help your friends see your recommendations, but again, that doesn’t matter if your friends aren’t on it. That record of where you’ve been is still the killer app.

Whenever you’re tired and you just want to go somewhere familiar, just open Foursquare and flick on the “You’ve been” filter. Every now and then, rate your past visits on Foursquare, and you’ll have a list of places you’ve “liked.” Now it’ll be easy to pick somewhere to meet up or to recommend to a visiting friend. All this takes minimal effort, and doesn’t require carefully curating lists, writing tips, or connecting with all your friends. And maybe you shouldn’t connect with your friends, even if you can.

What will you get from their occasional check- ins, besides FOMO, meaningless likes, and annoying updates about competing for points?

Virtual Delivery Agent (VDA) 7. Carl Stalhood. Navigation.

VMware 2. 10. 96. Video playback performance issue with hardware version 1. VMs in 2. D mode. For virtual desktops, give the virtual machine: 2+ v. CPU and 2+ GB of RAMFor Windows 2.

R2 RDSH, give the virtual machine 4 v. CPU and 1. 2- 2. 4 GB of RAMFor Windows 2. R2 RDSH, give the virtual machine 8 v.

CPU, and 2. 4- 4. GB of RAMRemove the floppy drive. Remove any serial or LPT ports. If v. Sphere. To reduce disk space, reserve memory. Memory reservations reduce or eliminate the virtual machine .

The NIC should be VMXNET3. If this VDA will boot from Provisioning Services. Give the VDA extra RAM for caching. Do not enable Memory Hot Plug. For v. Sphere, the NIC must be VMXNET3. For v. Sphere, configure the CD- ROM to boot from IDE instead of SATA.

SATA comes with VM hardware version 1. SATA won’t work with Pv. S. Install the latest version of drivers (e. VMware Tools). For more details, see CTX2. Intermittent Connection Failures/Black Screen Issues When Connecting from Multi- Monitor Client Machines to Windows 7 VDA with VDA 7. Sphere/ESXi. If v.

Sphere, disable NIC Hotplug. Users could use the systray icon to Eject the Ethernet Controller. Obviously this is bad. To disable this functionality, power off the virtual machine. Once powered off, right- click the virtual machine and click Edit. Settings. On the VM Options tab, expand Advanced and then click Edit Configuration.

Click Add. Row. On the left, enter devices. On the right, enter false.

Then click OK a couple times to close the windows. The VM can then be powered on. Windows Preparation. If RDSH, disable IE Enhanced Security Config. Optionally, go to Action Center (Windows 8.

R2) or Security and Maintenance (Windows 1. User Account Control and enable Smart. Screen . Run Windows Update. If Windows Firewall is enabled. Enable File Sharing so you can access the VDA remotely using SMBEnable COM+ Network Access and the three Remote Event Log rules so you can remotely manage the VDA.

Add your Citrix Administrators group to the local Administrators group on the VDA. The Remote Desktop Services “Prompt for Password” policy prevents Single Sign- on to the Virtual Delivery Agent. Check registry key HKEY.

If f. Prompt. For. Password = 1 then you need to fix group policy. The following GPO setting will prevent Single Sign- on from working. This hotfix solved a Personal v. Disk Image update issue detailed at Citrix Discussions. If this VDA is Windows Server 2.

R2, request and install the Windows hotfixes recommended by Citrix CTX1. Scroll down to see the list of recommended Microsoft hotfixes for Windows Server 2. R2. Ignore the Xen. App 6. x portions of the article. Also see http: //www. To remove the built- in apps in Windows 1.

Robin Hobo How to remove built- in apps in Windows 1. Enterprise. For Remote Assistance in Citrix Director, configure the GPO setting Computer Configuration . See Jason Samuel – How to setup Citrix Director Shadowing with Remote Assistance using Group Policy for more details. If you intend to use Citrix’s SCOM Management Packs for Xen. App/Xen. Desktop, make sure Win. RM is enabled on the VDA by running winrm quickconfig.

Install Virtual Delivery Agent 7. For virtual desktops, make sure you are logged into the console.

The VDA won’t install if you are connected using RDP. Make sure 8. 3 file name generation is not disabled. If so, see CTX1. 31.

User Cannot Launch Application in Seamless Mode to fix the App. Init. You can use the Command Line Installer to exclude Telemetry Service as detailed at VDA upgrade cmdlet at Citrix Discussions.

Xen. Desktop. VDASetup. Enable. Alternatively, you can download the standalone VDA package and run that instead. Click Start next to either Xen. App or Xen. Desktop.

The only difference is the product name displayed in the installation wizard. Click Virtual Delivery Agent for Windows Desktop OS or Windows Server OS depending on which type of VDA you are building. In the Environment page, select Create a Master Image and click Next. For virtual desktops, in the HDX 3. D Pro page, click Next.

In the Core Components page, if you don’t need Citrix Receiver installed on your VDA then uncheck the box. Click Next. In the Delivery Controller page, select Do it manually. Enter the FQDN of each Controller. Click Test connection. And then make sure you click Add.

Click Next when done. In the Features page, click Next.

If this is a virtual desktop, you can leave Personal v. Disk unchecked now and enable it later. In the Firewall page, click Next. In the Summary page, click Install. For RDSH, click Close when you are prompted to restart. After the machine reboots twice, login and installation will continue. Note: NT SERVICE\Citrix.

Telemetry. Service needs permission to login as a service. In the Call Home page, click Connect, enter your My. Citrix credentials, and then click Next. In the Finish page, click Finish to restart the machine again. If 8. 3 file name generation is disabled, see CTX1. User Cannot Launch Application in Seamless Mode to fix the App.

Init. When logging in through Citrix I got message “Wait for local session manager” for 2. When logging in to the server with RDS, I do not have to wait for this.”“Add the following 2 registry keys to your 7. VDA server – then try connecting to it using ICA to see if the issue still occurs: Add reg keys in “HKLM\SOFTWARE\Citrix\Group. Policy”Dword: “Cache.

Gpo. Expire. In. Hours” – Value = 5- 2. Hours) ***start with value of 5***Dword: “Gpo. Cache. Enabled” – Value = 1. Restart the machine after adding these registry keys and attempt an ICA connection (at least twice) to see if that helps the Login delay.”Controller Registration Port. Some environments will not accept the default port 8.

Virtual Delivery Agent registration. To change the port, do the following on the Virtual Delivery Agent: Open Programs and Features.

Find Citrix Virtual Delivery Agent and click Change. Click Customize Virtual Delivery Agent Settings. Edit the Delivery Controllers and click Next. On the Configure Delivery Controller page, change the port number and click Next. In the Summary page, click Reconfigure. In the Finish Reconfiguration page, click Finish.

You must also change the VDA registration port on the Controllers by running Broker. Service. exe /VDAPort. Controller Registration – Verify. If you restart the Virtual Delivery Agent machine or restart the Citrix Desktop Service. If you don’t see this then you’ll need to fix the List.

Of. DDCs registry key. You can also run Citrix’s Health Assistant on the VDA. Profile Management 5. Warning: If you are upgrading and have existing Windows 2.

R2 profiles based on the ! CTX! To fix it, run the following commands.

C: \Windows\Microsoft. NET\Framework. 64\v. The setting is called Auto- create PDF Universal Printer. Framehawk Configuration. To enable Framehawk, see http: //www.

Remote Desktop Licensing Configuration. On 2. 01. 2 R2 RDSH, the only way to configure Remote Desktop Licensing is using group policy (local or domain).

This procedure also works for 2. R2 RDSH. This procedure is not needed on virtual desktops. For local group policy, run gpedit. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Double- click Use the specified Remote Desktop license servers. Change it to Enabled and enter the names of the RDS Licensing Servers (typically installed on Xen. Desktop Controllers).

Click OK. Double- click Set the Remote Desktop licensing mode. Change it to Enabled and select Per User. Click OK. In Server Manager, open the Tools menu, expand Terminal Services and click RD Licensing Diagnoser. The Diagnoser should find the license server and indicate the licensing mode.

It’s OK if there are no licenses installed on the Remote Desktop License Server.