Surface pro 3 question

which surface pro 3 is good enough to run illustrator cc ?
there is quite a price difference between the basic model and the top of the line model

I have the I7 256GB model and it works just fine. The I5 may work, but I don't really recommend less than 8GB of ram. You will find the more ram the better. As it makes your entire system run faster. Unfortunately Microsoft only offers a 4GB or an 8GB model. It would be quite cool to be able to add more ram later on. Which you can not do. Though you can use a micro SD card for additional drive space. Frankly I should have gone with the 512GB drive as it would give me more options for what apps I can install.

Similar Messages

TWO Questions Before Signing Up - Surface Pro 3 + license related

I currently have CS6 and tested it on my Surface Pro 3 and the UI is so TINY its nearly usable. In everything I have read it appears the issue is on Adobe's end for not supporting windows higher resolutions or the calling to scale. Is there a known fix for this I am not seeing in the community? If I buy a license for Photoshop CC will it have the same scaling issues and micro sized user interface as CS6?
Question two is related to the license I purchase. Can I have the program on my desktop as well as my surface with a single license? Look forward to hearing back from someone, thanks in advance.

HiDPI and retina display support FAQ
One license entitles to two installations – though I’m not sure anymore if that’s for non-simultaneous use or is that condition has been dropped.

Surface Pro 3 Windows 8.1 Question

I have imaged a surface pro 3 with MDT but when swiping to the left there is no screen setting and I don't see an option for auto-brightness. Also, it doesn't appear that the surface will auto-rotate between landscape and portrait. Has anyone else seen
this problem?

Hi,
What do you mean by "when swiping to the left there is no screen setting"? what about the right edge? If you swipe to the right edge, can you see the charm bars? Win+C?
auto-brightness settings can be turned on by Change PC settings\PC and devices\Power and sleep\Brightness
https://www.microsoft.com/surface/en-us/support/personalization-and-ease-of-access/troubleshoot-surface-touchscreen-brightness?lc=1033
and you can check the auto-rotate settings though this guide:
http://www.microsoft.com/surface/en-us/support/hardware-and-drivers/troubleshoot-surface-touchscreen-rotation
Yolanda Zhu
TechNet Community Support

Bit Locker on surface pro 3 ssd card

I had a surface pro 3 which I managed to damage. There was data on the ssd that I needed so I have got it out and connected it to my laptop by usb. When I try and use open it, it comes up with bit locker drive encryption so I need a bitlocker recovery
key. help anyone?

Do you have the recovery key ? If you don't have it, I'm sorry to say but you'll loose all the data.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Type UI in CS6 in Surface Pro 3 is too small. Adobe needs to isuue a fix for CS6.

I don't need to upgrade CS6 for any photography reason. Adobe should make CS6 UI readable fro surface pro 3 users. They have a fix for later versions. Why not make it available in other earlier versions of photoshop. This is not a question of adding new features, it is a question of making the UI readable.

Mylenium wrote:
Nobody goes back to fix up a 5 year old software that was never meant to be run on computers that didn't exist back then.
However good software companies like Microsoft fixes bugs user report on their Current Software. Adobe should fix bugs on current marketed software like CS6 Adobe chooses not to. Microsoft fixed XP till the middle of 2014 years after windows 7 and win 8 were current. Bugs go unfixed in Photoshop release after release. Adobe Program support continues to be sub par year after year.
Currently there are three CS6
perpetual Mac version 13.0.6
perpetual PC version 13.0.1.3
subscription version 13.1.2 PC and Mac

Speed grade does not work on my surface pro 3

Two questions:
Speed grade does not work on my surface pro 3. It open normaly but when I import a video I ear only the sound the image is black.Why?
So I try to install it on a over computer but in the creativ cloud software I didn't it. Why ?

I would suggest you are wasting your time trying to use SG on a Surface Pro 3. SG minimum hardware specifications ask for a discrete GPU that supports a GPGPU language like CUDA http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-speedgrade.html
If you want to do colour correction then try using Adobe Premier effects such as the Fast Color Corrector or Curves.

Problem on Surface Pro 2

I've had no luck with power BI on a Surface Pro 2. I installed the app from the store. When I open it, it just goes to a blank blue screen.
I try to uninstall by pressing and holding and pressing uninstall. The startup icon is gone, but when I go to the store, it says the app is installed. Please help, this is tremendously frustrating. How do a force and uninstall so I can
update?

Yup, that is how I tried to uninstall. I click uninstall and seems to work. If I go to the store it shows install. When I reboot the power BI icon is back on my home screen.
Ace,
It looks like we need to take this offline with you to troubleshoot it. Please email me. It's edprice at Microsoft.
Thanks!
Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Can't PXE boot a Surface Pro 3 after already successfully imaging it

hey guys. To try to eliminate a lot of the initial question that come up with this issue, I figure I will start with established info. Our SCCM environment is healthy, and all images, drivers and apps are distributed to all of our DP's. We can image
PC's and laptops with no issue at all. We use network PXE booting. Using a 64 bit boot image. Needed drivers are injected into the boot image. Firmware on the Surface was updated. Using the Surface NIC dongle. THis dongle was only used to image
this Surface Pro 3 tablet one time. There is no record of the MAC of the dongle in SCCM since I deleted the Surface out, to make it an unknown again.
So, with a lot of trial and error, I was finally able to get this tab to PXE boot, and then successfully image. Was testing out the new windows 8.1 image I had built.
Since it ewas successful I wanted to add all of our apps to the TS and test them out in imaging. Well, I can no longer get this thing to PXE boot. It shows trying to Start PXE over IPv4, then just skips to IPv6, then boots up into windows.
I have delted the secure keys form ther BIOS, then reloaded them. I have tried hte full shut down method (Holding Volume Up and Power for 15 seconds, then waiting for 10 seconds or longer, then trying to PXE boot. I am getting a valid connection fro
mthe dongle.
Nothinhg I try works. Its tries to PXE boot over IPv4, but never gets there. But I can PXE boot any of our PC's or Laptops,m so its just an issue with this damn Surface Pro 3.
ANy advice?

So I finally got our server guy to enable the logging and get that smspxe.log file to be accessible. So here is the info from the log, when I attempt to PXE boot the Surface. I see the last 2 lines where it ignores the request, I just don't know why its
ignoring it.
PXE::CNotifyTimer::TimerSignalFunc SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::ProcessTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Potentially missed device 50:1A:C5:FE:D6:E9 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Cleared Old Devices: 1 / 1 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CBootImageManager::PurgeOldImages SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
Purging old images: 0 SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::Init SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::CancelTimer SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
PXE::CNotifyTimer::RegisterTimeout SMSPXE 4/14/2015 3:04:18 PM 8896 (0x22C0)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:347 1ad0230 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 57 Max DHCP Message Size: 05b8
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DF40 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:347 159d1f0 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 1=DHCPDiscover
    Type = 57 Max DHCP Message Size: 05b8
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:37 PM 5928 (0x1728)
ProcessMessage: Context:0241DE50 dTime:0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: DHCP Discover received. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 148, uncompressed size 298. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
MP_LookupDevice succeeded: 0 1 0 1 0 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: device is not in the database. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Initialized CStringStream object with string: c7c22c7d-4f40-49f1-b7ed-871c18a07b05;2015-04-14T19:04:37Z. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set enterpirse certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Set media certificate in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATIONEX SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Set authenticator in transport SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Setting message signatures. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Setting the authenticator. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
CLibSMSMessageWinHttpTransport::Send: URL: JAG-SCCM-01E.jonesapparel.com:443 CCM_POST /ccm_system_AltAuth/request SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
In SSL, but with no client cert SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7484 (0x1D3C)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 172.028.000.223
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
<============ SMSPXE 4/14/2015 3:04:37 PM 7484 (0x1D3C)
Request was successful. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
::DecompressBuffer(65536) SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Decompression (zlib) succeeded: original size 409, uncompressed size 950. SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName=""><Machine><ClientID>c70485df-9130-4b41-b61b-6c9e11b2f69a</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="10020125" OfferIDTime="4/2/2015 11:12:00 AM" PkgID="100000D0" PackageVersion="" PackagePath="xx
BootImageID="10000087" Mandatory="0"/></ClientIDReply>
SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
Client Identity: c70485df-9130-4b41-b61b-6c9e11b2f69a SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: SMSID=c70485df-9130-4b41-b61b-6c9e11b2f69a OfferID=10020125, PackageID=100000D0, PackageVersion=, BootImageID=10000087, PackagePath=http://JAG-SCCM-01E.jonesapparel.com/SMS_DP_SMSPKG$/10000087, Mandatory=0 SMSPXE 4/14/2015
3:04:37 PM 7480 (0x1D38)
50:1A:C5:FE:D6:E9, E65E7468-4CB9-210E-B760-54522B6A7E02: found optional advertisement 10020125 SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
============> Reply to client (DHCPDISCOVER): SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
DHCP message:
Operation: BootReply (2)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 0
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 172.028.000.223
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 2=DHCPOffer
    Type = 54 Server idenitifier: 172.028.000.223
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 60 ClassIdentifier: PXEClient SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
<============ SMSPXE 4/14/2015 3:04:37 PM 7480 (0x1D38)
[172.028.000.223:67] Recv From:[172.028.011.003:67] Len:359 1acbeb0 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
[172.028.000.223:67] Recv From:[172.028.011.002:67] Len:359 15a41f0 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
============> Received from client: SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.003
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 54 Server idenitifier: 172.028.000.015
    Type = 50 Requested IP: 172.028.011.052
    Type = 57 Max DHCP Message Size: ff00
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
DHCP message:
Operation: BootRequest (1)
Hardware Address type: 1
Hardware Address Length: 6
Hop Count: 1
Transaction ID: 24038353
Seconds Since Boot: 0
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 172.028.011.002
Hardware Address: 50:1a:c5:fe:d6:e9:
Magic Cookie: 63538263
Options:
    Type = 53 DHCP Message Type: 3=DHCPRequest
    Type = 54 Server idenitifier: 172.028.000.015
    Type = 50 Requested IP: 172.028.011.052
    Type = 57 Max DHCP Message Size: ff00
    Type = 55 Paramerter Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
    Type = 97 UUID: 0068745ee6b94c0e21b76054522b6a7e02
    Type = 94 UNDI: 010310
    Type = 93 Client system Arch: 0007
    Type = 60 ClassIdentifier: PXEClient:Arch:00007:UNDI:003016 SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
<============ SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
<============ SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)
Ignoring req from [172.028.011.003:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5928 (0x1728)
Ignoring req from [172.028.011.002:67] Dest Server:[172.028.000.015] SMSPXE 4/14/2015 3:04:40 PM 5972 (0x1754)

Lightroom Mobile on Surface Pro

I've been trying to find an answer to this question but have had no luck. I use Adobe Lightroom as part of my Creative Cloud Membership on my desktop for a majority of my photo editing. All is good there.
In Lightroom I've signed in and made some of my Collections editable on the cloud. I love that I can use my iPad or my Android Phone using the Lightroom Mobile App to do some light editing whenever I'm away from my desktop.
I have a Surface Pro tablet also and I would love to use my Surface Pro to edit photos when away from my desktop. My problem is it doesn't seem like Lightroom on the Surface has the same capabilities to edit the catalogs that I've set to be in the cloud.
Am I not understanding how Online/Mobile/Tablets work together or am I wanting to do something that isn't possible. It just seems like a Surface Pro 3 should be able to do what my iPad and phone can do.
I've read all about putting catalogs on dropbox and have the images on a removable drive and understand how that works, it just seems much more burdensome than the easier iPad/phone ease of use.
Thanks-Scott

You want to share LR and its photos on two desktop-capable systems. LR is a single-user program that needs the catalog attached locally.
The way I accomplish what you want is to have my LR catalog and photos on a portable USB3-attached 2TB drive and carry that with me. Because the drive is portable and subject to loss or theft or damage I backup my 2TB drive to another 2TB drive when I am at my main desktop computer. I basically copy everything on the main drive to the backup drive but using options in my backup program to only copy files that are different either in time-stamp or filesize which works out to my new photos, my LR catalog and some LR preview files. I have had the portable drive fail and merely replace my backup drive and use my former backup for my primary work, immediately, or as soon as I have copied things to the new backup drive.

Surface Pro 3 Type Cover Scrolling Behavior

I asked the same question in the surface comminity forum, and the support engineer suggested that I relay my question here.
I've just purchased a surface pro 3 with type cover. It's a great machine and I use it for web developement projects on the go. A major part of the stack I use has to be run in linux, so I run a virtual machine with ubuntu server. I use putty to ssh into
the vm, and rely on vim for code editing. On my previous machine I was able to get mouse scrolling support working in vim, as the events are relayed over by putty. This works even with 2 finger scrolling on trackpads of various sorts. However, this does not
work on the type cover for surface pro 3.
After some observations, I realized that the 2 finger scrolling on type cover's trackpad would trigger a screen scrolling animation when the scrollbars hit the end points, a behavior similar to scrolling via the touch screen. So I am guessing that instead
of using the traditional mouse wheel events, the new trackpad uses screen scrolling events? Which explains why putty couldn't relay the scrolling to vim.
I am wonder if this behavior can be optional or not. Perhaps a configuration somewhere would allow me to make the trackpad fire the usual mouse wheel like scrolling events so that my putty + vim combination could still benefit from the trackpad?

Hi,
Regarding Surface pro 3 type cover issue, we may first take a look at the following troubleshooting guide:
Troubleshoot your Surface Cover
For the type cover usage, please see:
Type Cover
Apologize for that we don't have enough materials to check the issue you mentioned here, for the usage of surface Pro 3 and its type cover, for special personal support, please take a try with the
Contact us.
Thank you for your understanding.
Best regards
Michael Shao
TechNet Community Support

Surface Pro 2 tries to use word in browser instead of client in SharePoint 2010 library

Hi -
A user came to me with a new surface pro 2 with IE 11 and Office 2013 and sadly found that document libraries would try to default open in the browser. I do not have the word app completely configured so it is unavailable. I have a Windows 8 laptop
with IE 11 working just fine, so I am having trouble pinpointing the issue on his device.
I have checked the settings at the library level, the site collection level, as well as the farm level to assure that all areas are configured to open in client app by default.
Has anyone ran into this?
Thanks,
Jesse
Jesse A. Brandenburg

As I mentioned. You add the second account by adding SharePoint Online as a Connected Service on the File menu in Word. You also need to make sure that they have updated the copy of Office on the Surface from the Home and Student version.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Can we access CM 14.0.2 on the Microsoft Surface Pro 3? It will have Microsoft 8.1 Pro on it.

My name is Cynthia and I work for Chicago Public Schools. We have approximately 400 users of the Primavera CM system. We've had challenges along the way with compatibility issues, but now here's a question I don't have an answer to.
Is the Surface Pro 3 any different and what are the Java requirements?

Hi Cynthia, Unfortunately CM 14.0.x has not been tested/certified against Win 8.1 as a web app server. Also there is no certification for integrating CM with MS Surface Pro. For more further information, please submit a SR within CM tech support. Regards, Matías G. Uribe.

Using a Mac and a Surface Pro with the same catalog?

I am using CC on my Mac as my primary computer. I'm thinking of getting a Surface Pro to use as a second computer.
1. Are there any issues with opening and saving a catalog back-and-forth between a Mac and a PC? I'm thinking of doing it via Dropbox.
2. Has anyone used LR on a Surface Pro? Can everything be done via touch? Does it work well? I'd like to mainly be able to go through all of my photos and tag and rate them on the Surface.
Thanks.

Using dropbox seems to be one of the choices people make when working with the same catalog on multiple computers. It reportedly works well as long as you ensure that you allow ample time for synchronization.
I cannot answer your question about the Surface Pro. You could download the trial version of Lightroom and evaluate for 30 days and then decide for yourself.
Adobe - Lightroom : For Windows : Adobe Photoshop Lightroom 5.7.1

Surface Pro Driver injection no longer working under MDT 2013

Since upgrading to MDT 2013 we are experiencing an issue with deploying Windows 8.1 to our Surface Pros. The deployment seems to be ignoring driver group settings in CS.ini and it basically injects no drivers. We are following the guide Microsoft posed here:
http://www.microsoft.com/en-us/download/details.aspx?id=38826
So I'm confused as to where we are going wrong. Here is the section in question from CS.ini:
[ByModel]
Subsection=Model-%Model%
[Model-Surface with Windows 8 Pro]
OSDComputerName=TAB%SerialNumber%
DriverGroup001="Windows 8.1 x64\Microsoft\Surface Pro"
DriverSelectionProfile=Nothing
XResolution=1920
YResolution=1080
Incidentally the computer name is getting set so i know this block is working. Any idea why the drivers would get skipped over?

I've been deploying to Surface tablets just fine and deployed to a Surface 3 just a couple days ago without any issues, but I do follow Johan's "Total control" way of managing drivers. http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
I'd recommend you go that way as well as you'll most likely have fewer issues. Depending on your situation you may also want to make use of the "ModelAliasExit" script and use Make variables or you can just follow the method above exactly as is.
If this post is helpful please vote it as Helpful or click Mark for answer.

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

Surface pro 3 question

Similar Messages

Maybe you are looking for