Remote Work Accessibility

Tired of setting up Revit for every user? Or are you even bold enough to leave it to the users themselves? In this video, I show how you can setup a new user profile with all standards, settings, and tools ready on first launch. The OS deployment already installs all core software - this script handles everything that lives in user folders and %appdata%. What the script configures: - Revit.ini - turns off Move on Drag - sets the default project template - sets selection and preselection colors - sets keyboard shortcuts - sets Revit Server Accelerator - creates rvtLocals folder structure - DynamoSettings.xml - pyRevit and CustomTools installation - pyRevit_config.ini - sets custom CSS for pyrevit - sets telemetry setting - sets tab coloring - runs the inventory script With this in place, starting Revit for the first time loads all extensions, settings, and defaults automatically. Dynamo Player opens the correct shared script directory, packages are ready, and the environment is consistent for each user from the first launch. A fully prepared workspace in minutes, without manual configuration. (The video is fast-forwarded in several places.) #revit #bim #automation

Top Strategies to Boost Virtual Machine Performance in VMware Environments CPU Performance: 1. Allocate sufficient CPU resources 2. Limit CPU overcommitment 3. Enable CPU hot-plugging (if supported) 4. Use CPU affinity (pin VMs to specific CPUs) 5. Monitor CPU usage and adjust allocations Memory Performance: 1. Allocate sufficient RAM 2. Configure memory reservations and limits 3. Enable memory hot-add (if supported) 4. Use memory ballooning (to reclaim unused memory) 5. Monitor memory usage and adjust allocations Storage Performance: 1. Use fast storage (e.g., SSD, NVMe) 2. Configure storage alignment (for optimal I/O) 3. Use thin provisioning (to reduce storage waste) 4. Enable disk caching (if supported) 5. Monitor storage I/O and adjust configurations Network Performance: 1. Allocate sufficient network resources 2. Configure network adapters (e.g., VMXNET3) 3. Enable network offloading (e.g., TCP offload) 4. Use jumbo frames (for increased throughput) 5. Monitor network usage and adjust configurations Virtual Machine Configuration: 1. Right-size VMs (avoid over/under-allocation) 2. Use the latest VM hardware version 3. Enable VM encryption (if required) 4. Configure VM swap files (to prevent disk thrashing) 5. Monitor VM performance and adjust configurations Host Configuration: 1. Ensure sufficient host resources 2. Configure host power management 3. Enable host caching (if supported) 4. Monitor host performance and adjust configurations 5. Regularly update host firmware and drivers vCenter Server Configuration: 1. Configure vCenter Server settings (e.g., statistics intervals) 2. Monitor vCenter Server performance 3. Adjust vCenter Server resource allocations 4. Use vCenter Server plugins (e.g., for storage management) 5. Regularly update vCenter Server software Best Practices: 1. Regularly monitor VM and host performance 2. Implement resource pools and reservations 3. Use vMotion and Storage vMotion (for load balancing) 4. Configure DRS (Distributed Resource Scheduler) 5. Follow VMware's performance guidelines Tools and Resources: 1. VMware vCenter Server 2. VMware ESXi 3. VMware Performance Manager 4. vRealize Operations Manager 5. VMware Knowledge Base articles By implementing these optimizations and best practices, you can significantly improve VM performance and ensure a seamless user experience.

Virtual Team Rooms ‘If you have a remote team, you can create a virtual team room using online tools. This works for hybrid and partially remote teams, too, but be careful: in-person conversations shut remote team members out. If some people are remote, the people working in person need to use the virtual team room for all their collaboration, too. A decision to use a virtual team room is a decision to act as if everyone is remote. Remote equipment and tools… Remote teams need an electronic version of the team workspace: - Videoconferencing software, such as Zoom, for real-time conversation - Messaging software, such as Slack, for asynchronous conversation - Virtual whiteboard software, such as Miro or Mural, for freeform, simultaneous collaboration - Collaborative versions of task-specific tools, where possible, such as Figma for UX and UI design - A document store, such as DropBox, Google Drive, or a wiki - Inexpensive tablets for collaborative whiteboard sketches - An additional monitor or tablet for videoconferencing, so people can see one another and work at the same time - For Delivering teams, collaborative programming tools, such as Tuple or Visual Studio Live Share, that support pairing or mobbing (see “Pair Programming” and “Mob Programming” for details) As with an in-person workspace, do not purchase Agile Lifecycle Management software or other tracking software. Designing remote collaboration Collaboration is easy when people are colocated. Achieving the same level of collaboration in a remote environment takes careful design. When your team establishes its working agreements during alignment chartering, make a point of discussing how you’ll collaborate. Remember that the goal is to maximize the performance of the team, not the individual. As work progresses, be sure to evaluate and improve your communication techniques frequently. I asked people who had experience with great in-person and remote collaboration experience for their remote collaboration tricks. There were several excellent suggestions: - Make time for personal connections. In-person teams form bonds of friendship and mutual respect, and this allows them to make decisions quickly and effectively. In a remote team, be sure to set aside time to socialize and keep up with each other’s lives. Options include virtual coffee breaks to help ease tension, a dedicated chat channel for greetings and personal updates as people arrive and leave their office, and a 30-minute call every day for chatting or playing games. One team made a habit of reserving the first 5–10 minutes of every meeting for socializing; people could either show up early to chat or just come for the content as their mood dictated. Another set aside time specifically for celebrating successes. - Ensure safety. In an...’ ― James Shore with Diana Larsen, Gitte Klitgaard, and Shane Warden, The Art of Agile Development https://lnkd.in/gEh4acmf

Working remotely can be both liberating and overwhelming. So I compiled the best remote workspace hacks to help you be productive. Setting Up Your Workspace ↳ Location Matters Choose a quiet, well-lit area with good ventilation. Position yourself away from loud environments (TV, busy rooms). Access natural light whenever possible for improved mood and energy. ↳ Ergonomics First Invest in an ergonomic chair and adjustable desk. Keep your screen at eye level and at least 20 inches away. Use a keyboard and mouse that minimize wrist strain. ↳ Technology Essentials Hardware: High-performance laptop/desktop, noise-canceling headphones, quality webcam. Software: Zoom, Microsoft Teams, Slack, Google Workspace. Connectivity: High-speed internet (at least 25 Mbps for video calls). ↳ Personalization Add personal touches like plants, photos, or motivational quotes. Use a desk organizer to keep essentials tidy. Adjust lighting to your preference (warm light for a cozy vibe). Which tip are you most excited to try first? Comment below! 👇 Want 30+ FREE AI resources? Enter your email here 👉 https://lnkd.in/eq75mzaT ♻️ Share this post to help others design their ultimate remote workspace!

Stop Wasting Time on VM Deployment! Automate with vSphere OS Customization Policies 🚀 Tired of manually configuring every single VM in your vSphere environment? Renaming, assigning IPs, running sysprep, activating Windows licenses, and joining domains one by one is a huge time sink! Especially in larger deployments, this process can be incredibly tedious and prone to errors. Thankfully, VMware vSphere offers a powerful solution: OS Customization Policies! This game-changing feature allows you to automate the entire VM customization process, significantly reducing deployment time and ensuring consistency across your virtual infrastructure. Imagine deploying dozens, even hundreds, of VMs with just a few clicks, each pre-configured with the correct settings. That's the power of OS Customization! Here's how OS Customization Policies can revolutionize your workflow: * Automated Configuration: Define all the necessary settings (hostname, IP address, domain join, Windows activation, etc.) in a policy. When you deploy a VM, these settings are automatically applied. * Reduced Manual Effort: Say goodbye to repetitive tasks! Free up your valuable time to focus on more strategic initiatives. * Consistency and Standardization: Ensure every VM is configured identically, eliminating inconsistencies and reducing troubleshooting headaches. * Faster Deployments: Spin up new VMs in a fraction of the time, accelerating your development and testing cycles. * Simplified Management: Centrally manage all your customization settings through policies, making updates and changes a breeze. Key features of vSphere OS Customization: * Support for Multiple Guest Operating Systems: Customize Windows, Linux, and other supported OSs. * Integration with vCenter Server: Manage policies and apply them seamlessly during VM deployment. * Flexible Configuration Options: Customize everything from network settings to user accounts and software installations. * Sysprep Integration: Leverage sysprep for Windows deployments to ensure unique SIDs and avoid conflicts. Who can benefit from OS Customization Policies? * Cloud Providers: Quickly provision and customize VMs for their customers. * Large Enterprises: Streamline VM deployments and maintain consistency across their infrastructure. * IT Administrators: Simplify daily tasks and reduce the risk of human error. * DevOps Teams: Accelerate the deployment of development and testing environments. Stop struggling with manual VM configuration! Embrace the power of OS Customization Policies in vSphere and unlock a new level of efficiency in your virtual infrastructure management. #VMware #vSphere #OSCustomization #Automation #Virtualization #CloudComputing #ITInfrastructure #SysAdmin #DevOps #Efficiency #TechTips #مسؤول_أنظمة #أمن_معلومات #مراكز_بيانات #تقنية_معلومات #تحول_رقمي #حوسبة_سحابية

🚀 Complete Step-by-Step VDI Deployment Guide for Beginners 👨💻🖥️ Over the past few weeks, I’ve compiled a comprehensive VDI Infrastructure Deployment Guide — perfect for freshers, system admins, and virtualization learners. This guide walks through 9 practical phases using VMware Horizon to help you build a fully functional Virtual Desktop Infrastructure (VDI) environment from scratch. 📌 What’s covered? 1️⃣ Planning & Prerequisites – From clone types to hardware/network planning 2️⃣ ESXi & vCenter Setup – Foundation of virtualization 3️⃣ Active Directory Configuration – AD, OUs, users, permissions 4️⃣ Horizon Connection Server & Events DB – Core services and logs 5️⃣ SQL Server Setup – Event logging and Composer (optional) 6️⃣ Golden Image & Desktop Pool – Instant Clone deployment, OS optimization 7️⃣ Client Connectivity – Horizon Client, session validation 8️⃣ Unified Access Gateway (UAG) – External secure access 9️⃣ Monitoring & Maintenance – Built-in tools + Zabbix agent-based monitoring ✅ Includes a final checklist for validation and long-term maintenance. 📄 Download the full guide in PDF format: 💬 If you’re just starting out with virtualization or planning a VDI rollout, this guide is for you. Would love to connect with others working on Horizon deployments — feel free to share your experience or feedback! #VMwareHorizon #VDI #SystemAdmin #Virtualization #CloudDesktop #HorizonView #Wintel #ActiveDirectory #vCenter #Zabbix #VDIDeployment #TechForFreshers #LinkedInLearning #CareerInTech #CloudInfra #DevOpsJourney #LabSetup #InfrastructureEngineer #RemoteDesktop #DigitalWorkspace

The non-coder’s guide to Claude Cowork. 10 things to set up before you do anything else. I've been building with Claude Code for months, and I set up Cowork configurations for non-technical business owners as part of my consulting work. Most people set it up wrong because they skip the first 30 minutes of configuration. These steps fixes that. ⏰ Import your ChatGPT memory: - Don't start over; transfer your ChatGPT history in 60 seconds - Claude should knows your business and writing style. ⏰ Set Global Instructions: - Spend 5 minutes writing permanent rules about who you are + how you work - Go to Settings > Cowork tab > Click "Edit" on Global Instructions ⏰ Enable "Plan Mode": - Add a rule saying "Always show a plan. Wait for my approval" - It prevent the AI from modifying your computer files without your permission. ⏰ Build a Workspace: - Create specific folders for your current projects and "successful examples" - Helps Claude to reverse-engineer and copy your absolute best work. ⏰ Install Plugins: - Turn Claude from a generalist into a specialist by installing workflow tools, - Start with Anthropic's Productivity plugin. ⏰ Connect Slack: - Allow Claude to read your channels - It summarizes important updates, and draft replies for your approval. ⏰ Connect Google Calendar: - Give it access to check your schedule - It finds open times, and automatically prepare you for upcoming meetings. ⏰ Connect Gmail: - Have Claude analyze your past sent emails to extract your tone - It drafts new replies that sound exactly like you. ⏰ Build Custom Skills: - Save specific instructions for recurring tasks (like writing posts or meeting agendas) - Write simple instructions for 3-5 tasks you do often ⏰ Schedule a Daily Briefing: - Set an automatic 8 AM task for Claude to scan your Slack, email, and calendar - It’ll give a neat prioritized summary before you even open your laptop. Taking the time to build this configuration is the exact difference between …an AI you use sometimes, and an AI that actively works for you. What is the very first daily task you would hand off to your new AI employee? ♻️ Share with your network ➕ Follow for more AI educational content ___________________________________________ 👋 I’m Amit Rawal, an AI practitioner and educator. Outside of work, I’m building SuperchargeLife.ai , a global movement to make AI education accessible and human-centered. ♻️ Repost if you believe AI isn’t about replacing us… It’s about retraining us to think better. Opinions expressed are my own in a personal capacity and do not represent the views, policies, or positions of my employer (currently Google LLC) or its subsidiaries or affiliates.

Remote development environments are all the rage, but starting from scratch is difficult. This is a quick post to get you off the ground by comparing GitHub Codespaces and GitLab / Gitpod Workspaces. You can start a - GH Codespace: in a repository, click Code->Codespaces->Create codespace on main - GP Workspace: on Gitlab in a repository, click Edit->Gitpod But what do you need for these to be meaningful? For a codespace, you need a "devcontainer.json" in the ".devcontainer" directory. The content is just a plain JSON, as you can see below, describing: - Number of CPUs for the codespace (4) - Instructions for the container image (Ubuntu with Python) - Customisations, for example, which VSCode extensions will be installed in the remote environment (python relevant extensions) - Environment variables that will be set on the new machine - A startup shell command where you can do custom instructions (download a different version of Python with pyenv, create a virtual environment, or anything else; more on this in the next post) For a workspace, you need a ".gitpod.yml" in the root repo directory: - Instructions for the container (This example uses the default, called "Workspace-Full") - A shell script to run at startup (same as with codespaces) - VSCode extensions (same as with codespaces. The only difference is that you can only use open-source extensions as Gitpod uses a different source than Github (which is MicroSoft). - And some ports to be open at startup if you need to run, for example, a notebook server or test a local FastAPI deployment. And that's it... As you can see, both of them refer to a ".devcontainer/setup.sh". More on this in the next post. You can ask why the gitpod one refers to the ".devcontainer" directory, and that's because these examples are from our training program, where we maintain the two versions in a single project. I hope you find this helpful and give it a try. Both places have generous free compute for experimentation. Next: GitHub Actions vs Gitlab Pipelines.

As founder of a fully remote company spread across 3 continents whose formative years took place during the height of the pandemic, I've given a lot of thought to virtual offices. Done right, a virtual office can maintain productivity, foster collaboration, and nurture company culture. Done wrong, a virtual office quickly becomes an expensive, unused ghost town. If you're considering a virtual office, here are the top 10 things you should look for: 1. Infinite Spaces and Creativity: Look for a platform that offers unlimited spaces, allowing you to create multiple offices, meeting rooms, and collaborative spaces without constraints. 2. Employee-Created Spaces: Empower your team to create and customize their own spaces. This not only promotes engagement but also lets employees personalize their work environments, fostering a sense of ownership. 3. Interactive Experiences. At Topia, our SDK and Experience Engine allow you to create or remix interactive experiences. This is particularly valuable for building social applications or training simulations, setting your virtual office apart from standard setups. 4. Data Ownership: Ensure that you own all your data. At Topia, we solve for this by offering dedicated deployments, that give you full control over your database, protecting your IP and maintaining privacy. 5. Scalability: The platform should support an unlimited number of guests without additional costs. Scalable technology is essential for large events or company-wide meetings. 6. Multiple Modes of Interaction: A strong virtual office should offer multiple communication modes, including text chat, audio, video, and proximity-based interactions. This flexibility supports various work styles and enhances team collaboration. 7. Persistent Environments: Look for a platform where spaces remain available and customizable 24/7. This allows employees to engage in impromptu meetings, after-hours collaboration, or casual social interactions whenever needed. 8. Robust Analytics: Choose a platform with comprehensive analytics that provide insights into engagement, social connections, and productivity. This data is invaluable for refining your virtual office setup and optimizing team performance. 9. Seamless Integration with Existing Tools: The virtual office should integrate smoothly with your current systems. This integration streamlines workflows and reduces the need for additional training. 10. Lightweight and Easy To Use. Your virtual office shouldn't require employees to purchase VR equipment or run heavyweight applications. Topia can be accessed through a browser or mobile device, no downloads or applications necessary.

𝐌𝐀𝐆𝐍𝐄𝐓𝟒 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤 𝐭𝐨 𝐆𝐞𝐭 𝐂𝐥𝐢𝐞𝐧𝐭𝐬 𝐚𝐬 𝐚 𝐕𝐀 #𝟐 𝐄𝐪𝐮𝐢𝐩𝐦𝐞𝐧𝐭 𝐚𝐧𝐝 𝐓𝐨𝐨𝐥𝐬 Having dependable equipment is the backbone of professional remote work. When your hardware, internet connection, and software run smoothly, clients see you as reliable and worth every dollar. 𝐖𝐡𝐲 𝐢𝐭 𝐦𝐚𝐭𝐭𝐞𝐫𝐬 → Downtime means missed deadlines and lost income. → Clear audio and video create stronger client rapport. → Fast, secure systems speed up delivery and protect sensitive data. 𝐄𝐬𝐬𝐞𝐧𝐭𝐢𝐚𝐥𝐬 → Laptop/desktop: at least 8 GB RAM, SSD, Intel i5 / Ryzen 5 or better. → Noise-canceling USB headset for crisp calls. → Fiber or 5 G internet (minimum 50 Mbps) plus mobile-hotspot backup. → Uninterruptible Power Supply (UPS) to stay online during outages. → Dual monitors for efficient multitasking. → 1080p webcam for clear video meetings. → Password manager and updated antivirus for security. → Core software stack: project management (Trello, ClickUp), communication (Slack, Teams), and automation tools (Zapier, Make). 𝐎𝐭𝐡𝐞𝐫 𝐁𝐫𝐨-𝐓𝐢𝐩𝐬: → Log a weekly internet speed test and keep screenshots as proof for clients. → Schedule quarterly tech check-ups to update software, clean hardware, and audit passwords. → Prioritize uptime gear (UPS, backup router) before cosmetic add-ons. → Learn keyboard shortcuts and set up macros to cut repetitive work. → Keep a small Plan B kit: portable Wi-Fi, spare mouse, extra headset pads. 𝐑𝐞𝐦𝐞𝐦𝐛𝐞𝐫: Your setup is your storefront. A stable, efficient workspace reassures clients that you can support their business without interruption therefore making it easier for them to choose and retain you.