Can WinPE be used as server? Can WinPE be used to host file shares? I searched and didn’t really find a definite answer out there. One Microsoft page said no. But the actual answer is yes. Of course, most people only know/use WinPE for imaging, system repair, and data rescue.

Let me explain my need. I use the “swing migration” process when migrating to new server hardware. I’ve tried the other migration options. They either force me to change the server name or want me to rebuild some/all of the environment. Now when using the “swing migration” my original server and new server both have the same name. They both are domain controllers for the same AD forest. Therefore renaming is not possible and they should never actually be on the same network. How to move the data? There’s a few ways but I prefer to use WinPE. This allows me to move the data without booting in to the original operating system.

I’ve only done this with WinPE 10 so far. But here’s how it can be done. I use a simple batch file.

net user admin password /add
net localgroup administrators admin /add
net share /y
wpeutil disablefirewall
ipconfig | find “IPv4”

Explained. Line 1, creates a new user called admin and assigns it a password. Line 2, adds the admin user to the administrators group. Line 3, starts the server service. Line 4, disables the firewall. Line 5, shows the IP address of the system.

This allows access to the administrative shares (i.e. C$, D$, etc.). Connect to the shares via \\{ip address}\{share name}. You could probably create other shares using the net share command. My needs didn’t require it. As I mentioned earlier a temporary server, WinPE has 72 hour use limit and will restart automatically when reached.

Recently needed to setup a Mac system to connect via XenApp 6.5. It was failed during the login process. I had previously connected via a Windows Citrix Receiver client using the same credentials. So why isn’t it working on with Receiver for Mac? I checked the event logs. There it was –  “Error – 40005 – XenApp Services – An error occurred while launching a user’s resource: ClientName is null, over-length or contains invalid characters”. Receiver for Mac uses the computer’s name as the client name. I went to Menu Bar->Apple Menu->System Preferences->Sharing. I found the computer name had a ” (double quote) within it. Once I removed the double quote from the computer name, it was able to login.

As of October 15th, 2016 all calls within the 317 area code will require ten digit dialing. If all ten digits are not used you’ll likely get the message “Your call cannot be completed as dialed. Please try your call again”. Ten digit dialing is already supported so start doing it now. This way you’ll already be in the habit and the deadline won’t effect you. But there’s more to be done. All phone devices need to be reviewed. Phone entries need to be checked to make sure include the area code. This includes stored numbers in cell phones, fax machines, speed dials and any type of stored number. Also some devices may be configured to only dial ten digits for those area codes outside of 317. Now it must now all the necessary ten digits for 317 and the new 463 area code. It must not dial a 1+ten digits unless it’s truly a long distance call. If it does so the call will  not go through. This article has information on the deployment of the new 463 area code. If you need assistance or don’t know where to start, please contact us.

Are you still using Windows SQL Server 2005? It was very popular and widely deployed. Many businesses are still be using it today. It’s being End Of Life (EOL)/retired by Microsoft in next April (04/12/2016). This means no more technical support or security updates. Businesses that continue to use it may be putting themselves at risk. It’s recommended you upgrade/replace it with one of Microsoft’s newer SQL Server products. We can assist you with getting it updated to one of Microsoft’s newer and supported SQL products.

Are you still using Microsoft Windows Server 2003? It was a very popular and widely deployed product. Many businesses are still be using it today. It’s being End Of Life (EOL)/retired by Microsoft in July (07/15/2015). This means no more technical support or security updates. Businesses that continue to use it may be putting themselves at risk. It’s recommended they upgrade or replace it with one of Microsoft’s newer server operating systems. We can assist you with getting updated and making sure you are on a stable and supported Microsoft server product.